View USS-820D_2103933.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

data sheet, rev. 4 june 2001 USS-820D usb device controller features full compliance with the universal serial bus specification revision 1.1 . backward compatible with uss-820b and uss-820c revisions. self-powered or bus-powered usb device. meets usb power specifications for bus-powered devices. full-speed usb device (12 mbits/s). usb device controller with protocol control and administration for up to 16 usb endpoints. supports control, interrupt, bulk, and isochronous transfers for all 16 endpoints. programmable endpoint types and fifo sizes and internal 1120-byte logical (2240-byte physical for dual-packet mode) shared fifo storage allow a wide variety of configurations. dual-packet mode of fifos reduces latency. supports usb remote wake-up feature. on-chip crystal oscillator allows external 12 mhz crystal or 3 v/5 v clock source. on-chip analog pll creates 48 mhz clock from internal 12 mhz clock. integrated usb transceivers. 5 v tolerant i/o buffers allow operation in 3 v or 5 v system environments for 0 c to 70 c tempera- ture range. 5 v tolerant i/o buffers allow operation in 3 v only system environments for ?20 c to +85 c temper- ature range. implemented in agere systems inc. 0.25 m, 3 v standard-cell library. 44-pin mqfp (USS-820D). 48-pin tqfp (uss-820td). evaluation kit available. new features after revision b new, centralized fifo status bits and interrupt out- put pin reduce firmware load. new, additional nonisochronous transmit mode allows nak response to cause interrupt. isochronous behavior enhancements simplify firm- ware control. additional fifo sizes for nonisochronous end- points. usb reset can be programmed to clear device address. usb reset output status pin. firmware ability to wake up and reset a suspended device. lower power. 5 v supply no longer required for 5 v tolerant oper- ation. applications suitable for peripherals with embedded micropro- cessors. glueless interface to microprocessor buses. support of multifunction usb implementations, such as printer/scanner and integrated multimedia applications. suitable for a broad range of device class periph- erals in the usb standard. note: advisories are issued as needed to update product information. when using this data sheet for design purposes, please contact your agere systems account manager to obtain the latest advisory on this product.
table of contents contents page data sheet, rev. 4 june 2001 usb device controller USS-820D 2 agere systems inc. features ....................................................................................................................... .............................................1 new features after revision b .................................................................................................. ...............................1 applications ................................................................................................................... ............................................1 description.................................................................................................................... .............................................3 serial interface engine........................................................................................................ .................................... 3 protocol layer ................................................................................................................. ........................................ 4 fifo control ................................................................................................................... ........................................ 4 fifo programmability ........................................................................................................... ..................................4 fifo access .................................................................................................................... ....................................... 4 transmit fifo .................................................................................................................. .................................... 5 receive fifo ................................................................................................................... .................................... 6 pin information ............................................................................................................... ..........................................7 register timing characteristics................................................................................................ .................................9 register interface ............................................................................................................. .......................................12 special firmware action for shared register bits ............................................................................... .................14 register reads with side effects............................................................................................... ...........................15 register descriptions .......................................................................................................... ..................................16 interrupts ..................................................................................................................... ............................................41 firmware responsibilities for usb setup commands............................................................................... ...........42 other firmware responsibilities................................................................................................ ..............................43 frame timer behavior........................................................................................................... ..................................43 suspend and resume behavior.................................................................................................... ..........................43 hardware suspend detect........................................................................................................ ............................44 firmware suspend initiate ...................................................................................................... ..............................44 hardware resume detect/initiate ................................................................................................ .........................45 hardware resume sequence ....................................................................................................... ........................45 firmware resume sequence ....................................................................................................... ........................45 special suspend considerations for bus-powered devices ......................................................................... .......45 application notes.............................................................................................................. .......................................47 absolute maximum ratings....................................................................................................... ..............................47 electrical characteristics ..................................................................................................... ....................................48 dc characteristics ............................................................................................................. ....................................48 power considerations ........................................................................................................... .............................49 usb transceiver driver characteristics ......................................................................................... ......................49 connection requirements ........................................................................................................ ............................50 usb transceiver connection ..................................................................................................... ........................50 oscillator connection requirements............................................................................................. .....................51 outline diagrams............................................................................................................... ......................................52 44-pin mqfp (USS-820D)......................................................................................................... ...........................52 48-pin tqfp (uss-820td) ........................................................................................................ ..........................53 ordering information........................................................................................................... .....................................53 appendix a. special function register bit names................................................................................ ..................54 appendix b. USS-820D register map.............................................................................................. .......................55 appendix c. changes from uss-820/uss-825 revision b to c ....................................................................... .....56 appendix d. changes from uss-820/uss-820t revision c to d ...................................................................... ....57
data sheet, rev. 4 june 2001 agere systems inc. 3 usb device controller USS-820D description 5-8121 figure 1. block diagram usb fifo sie protocol layer external microprocessor dpls dmns control xcvr digital bus v ss v dd fifos USS-820D oscillator pll pll USS-820D is a usb device controller that provides a programmable bridge between the usb and a local microprocessor bus. it is available in two package types: 44-pin mqfp (USS-820D) and 48-pin tqfp (uss-820td, formerly uss-825). the USS-820D allows pc peripherals to upgrade to usb connectivity without major redesign effort. it is programmable through a simple read/write register interface that is compatible with industry-standard usb microcontrol- lers. USS-820D is designed in 100% compliance with the usb industry standard, allowing device-side usb prod- ucts to be reliably installed using low-cost, off-the-shelf cables and connectors. the integrated usb transceiver supports 12 mbits/s full-speed operation. fifo options support all four transfer types: control, interrupt, bulk, and isochronous, as described in universal serial bus specification revision 1.1, with a wide range of packet sizes. its double sets of fifo enable the dual-packet mode feature. the dual-packet mode feature reduces latency by allowing simultaneous transfers on the host and microprocessor sides of a given unidirectional endpoint. the USS-820D supports a maximum of eight bidirec- tional endpoints with 16 fifos (eight for transmit and eight for receive) associated with them. the fifos are on-chip, and sizes are programmable up to a total of 1120 logical bytes. when the dual-packet mode feature is enabled, the device uses a maximum of 2240 bytes of physical storage. this additional physical fifo stor- age is managed by the device hardware and is trans- parent to the user. the fifo sizes supported are 8 bytes, 16 bytes, 32 bytes, and 64 bytes for nonisochronous pipes, and 64 bytes, 256 bytes, 512 bytes, and 1024 bytes for iso- chronous pipes. the fifo size of a given endpoint defines the upper limit to maximum packet size that the hardware can support for that endpoint. this flexibility covers a wide range of data rates, data types, and combinations of applications. the USS-820D can be clocked either by connecting a 12 mhz crystal to the xtal1 and xtal2 pins, or by using a 12 mhz external oscillator. the internal 12 mhz clock period, which is a function of either of these clock sources, is referred to as the device clock period (t clk ) throughout this data sheet. serial interface engine the sie is the usb protocol interpreter. it serves as a communicator between the USS-820D and the host through the usb lines. the sie functions include the following: package protocol sequencing. sop (start of packet), eop (end of packet), resume, and reset signal detection and genera- tion. nrzi data encoding/decoding and bit stuffing. crc generation and checking for token and data. serial-to-parallel and parallel-to-serial data conver- sion.
4 4 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D description (continued) protocol layer the protocol layer manages the interface between the sie and fifo control blocks. it passes all usb out and setup packets through to the appropriate fifo. it is the responsibility of firmware to correctly interpret and execute each usb setup command (as docu- mented in the firmware responsibilities for usb setup commands section) via the register interface. the protocol layer tracks the setup, data, and status stages of control transfers. fifo control USS-820D?s fifo control manager handles the data flow between the fifos and the device controller?s pro- tocol layer. it handles flow control and error handling/ fault recovery to monitor transaction status and to relay control events via interrupt vectors. fifo programmability table 1 shows the programmable fifo sizes. the size of the fifo determines the maximum packet size that the hardware can support for a given endpoint. an end- point is only allocated space in the shared fifo stor- age if its rxepen/txepen bit = 1. if the endpoint is disabled (rxepen/txepen = 0), it is allocated 0 bytes. register changes that affect the allocation of the shared fifo storage among endpoints must not be made while there is valid data present in any of the enabled endpoints? fifos. any such changes will ren- der all fifo contents undefined. register bits that affect the fifo allocation are the endpoint enable bits (the txepen and rxepen bits of epcon), the size bits of an enabled endpoint (ffsz bits of txcon and rxcon), the isochronous bit of an enabled endpoint (txiso bit of txcon and rxiso bit of rxcon), and the feat bit of the mcsr register. if the mcsr.feat register bit is set to 1, additional fifo sizes are enabled for nonisochronous endpoints, as shown in table 1. table 1. programmable fifo sizes * assumes mcsr.feat = 1. if this bit is 0 and ffsz = 10 or 11, both indicate a size of 64 bytes. each fifo can be programmed independently via the txcon and rxcon registers, but the total logical size of the enabled endpoints (tx fifos + rx fifos) must not exceed 1120 bytes. the 1120-byte total allows a configuration with a full-sized, 1024-byte isochronous endpoint, a minimum-sized, 64-byte isochronous feed- back endpoint, and the required, bidirectional, 16-byte control endpoint. when the dual-packet mode feature is enabled, the device uses a maximum of 2240 bytes of physical storage. this additional physical fifo stor- age is managed by the device hardware and is trans- parent to the user. fifo access the transmit and receive fifos are accessed by the application through the register interface (see tables 22?25 for transmit fifo registers and tables 26?29 for receive fifo registers). the transmit fifo is written to via the txdat register, and the receive fifo is read via the rxdat register. the particular transmit/receive fifo is specified by the epindex register. each fifo is accessed serially, each rxdat read increments the receive fifo read pointer by 1, and each txdat write increments the transmit fifo write pointer by 1. each fifo consists of two data sets to provide the capability for simultaneous read/write access. control of these pairs of data sets is managed by the hard- ware, invisible to the application, although the applica- tion must be aware of the implications. the receive fifo read access is advanced to the next data set by firmware setting the rxffrc bit of rxcon. this bit clears itself after the advance is complete. the transmit fifo write access is advanced to the next data set by firmware writing the byte count to the txcnth/l regis- ters. the usb access to the receive and transmit fifos is managed by the hardware, although the control of the nonisochronous data sets can be overridden by the arm and atm bits of rxcon and txcon, respec- tively. a successful usb transaction causes fifo access to be advanced to the next data set. a failed usb transaction (e.g., for receive operations, fifo overrun, data time-out, crc error, bit stuff error; for transmit operations, fifo underrun, no ack from host) causes the fifo read/write pointer to be reversed to the beginning of the data set to allow transmission retry for nonisochronous transfers. ffsz[1:0] 00 01 10 11 nonisoch- ronous 16 bytes 64 bytes 8 bytes* 32 bytes* isochro- nous 64 bytes 256 bytes 512 bytes 1024 bytes
agere systems inc. 5 data sheet, rev. 4 june 2001 usb device controller USS-820D description (continued) fifo access (continued) transmit fifo the transmit fifos are circulating data buffers that have the following features: support up to two separate data sets of variable sizes (dual-packet mode). include byte counter register for storing the number of bytes in the data sets. protect against overwriting data in a full fifo. can retransmit the current data set. all transmit fifos use the same architecture (see figure 2). the transmit fifo and its associated logic can man- age up to two data sets: data set 0 (ds0) and data set 1 (ds1). since two data sets can be used in the fifo, back- to-back transmissions are supported. dual-packet mode for transmit fifos is enabled by default. single-packet mode can be enforced by firmware convention (see txfif register bits). the cpu writes to the fifo location that is specified by the write pointer. after a write, the write pointer automati- cally increments by 1. the read marker points to the first byte of data written to a data set, and the read pointer points to the next fifo location to be read by the usb interface. after a read, the read pointer automatically incre- ments by 1. when a good transmission is completed, the read marker can be advanced to the position of the read pointer to set up for reading the next data set. when a bad transmission is completed, the read pointer can be reversed to the position of the read marker to enable the function interface to reread the last data set for retransmission. the read marker advance and read pointer reversal can be achieved two ways: explicitly by firmware or automatically by hardware, as indicated by bits in the transmit fifo control register (txcon). 5-5206 figure 2. transmit fifo read pointer write pointer read marker txcnth txcntl byte count registers from cpu cpu writes to fifo to usb interface data set 0 data set 1 sie reads fifo advrm revrp txdat
6 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D description (continued) fifo access (continued) receive fifo the receive fifos are circulating data buffers that have the following features: support up to two separate data sets of variable sizes (dual-packet mode). include byte count register that accesses the number of bytes in data sets. include flags to signal a full fifo and an empty fifo. can reread the last data set. figure 3 shows a receive fifo. a receive fifo and its associated logic can manage up to two data sets: data set 0 (ds0) and data set 1 (ds1). since two data sets can be used in the fifo, back-to-back transmissions are supported. single-packet mode is established by default after a USS-820D device reset, which sets the rxspm register bit. firmware can enable dual-packet mode by clearing the rxspm bit to 0. the receive fifo is symmetrical to the transmit fifo in many ways. the sie writes to the fifo location specified by the write pointer. after a write, the write pointer automatically increments by 1. the write marker points to the first byte of data written to a data set, and the read pointer points to the next fifo location to be read by the cpu. after a read, the read pointer automatically increments by 1. when a good reception is completed, the write marker can be advanced to the position of the write pointer to set up for writing the next data set. when a bad transmission is completed, the write pointer can be reversed to the posi- tion of the write marker to enable the sie to rewrite the last data set after receiving the data again. the write marker advance and write pointer reversal can be achieved two ways: explicitly by firmware or automatically by hardware, as specified by bits in the receive fifo control register (rxcon). the cpu should not read data from the receive fifo before all bytes are received and successfully acknowledged because the reception may be bad. to avoid overwriting data in the receive fifo, the sie monitors the fifo full flag (rxfull bit in rxflg). to avoid reading a byte when the fifo is empty, the cpu can monitor the fifo empty flag (rxemp bit in rxflg). the cpu must not change the value of the epindex register during the process of reading a data set from a par- ticular receive fifo. once the cpu has read the first byte of a data set, the processor must ensure that the epin- dex register setting remains unchanged until after the last byte is read from that data set. registers other than epindex may be read or written during this period, except for registers which affect the overall fifo configuration, as described in the fifo programmability section. if epindex is allowed to change during a data set read, incor- rect data will be returned by the USS-820D when subsequent bytes are read from the partially read data set. there is no such restriction when writing fifos. 5-5207 figure 3. receive fifo write pointer read pointer write marker rxcnth rxcntl byte count registers to cpu cpu reads fifo from usb interface data set 0 data set 1 sie writes to fifo rxdat
agere systems inc. 7 data sheet, rev. 4 june 2001 usb device controller USS-820D pin information 5-8117 figure 4. USS-820D pin diagram (44-pin mqfp) 5-8118 figure 5. USS-820D pin diagram (48-pin tqfp) 1 3 4 5 6 7 8 9 10 11 2 44 42 41 40 39 38 37 36 35 34 43 12 14 15 16 17 18 19 20 21 22 13 33 31 30 29 28 27 26 25 24 23 32 wrn nc iocsn sofn irqn suspn rwupn v ssx v ddt xtal2 xtal1 dpls v sst a0 a1 a2 v dda dmns reset v dd1 d2 v ss2 d3 d1 d0 d4 d5 d6 d7 v ssx rdn v ssx v ss0 v ssx v ssx v ss1 usbr a4 nc dsa dppu a3 v dd0 v ssx nc v dda xtal1 xtal2 v ddt dmns dpls v sst a0 a1 a2 1 2 3 4 5 6 7 8 9 10 11 a3 12 36 35 34 33 32 31 30 29 28 27 26 rdn wrn iocsn nc reset sofn irqn suspn rwupn nc v ssx 25 v ssx a4 v ss0 dsa nc v dd0 usbr nc nc v ss1 v ssx 13 14 15 16 17 18 19 20 21 22 23 v ssx 24 48 47 46 45 44 43 42 41 40 39 38 dppu v dd1 d0 d1 d2 v ss2 d3 d4 d5 d6 d7 37 v ssx v ssx
8 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D pin information (continued) table 2. pin descriptions * active-low signals within this document are indicated by an n following the symbol names. ? pins marked as nc must have no external connections, except where noted. 44-pin mqfp (USS-820D) 48-pin tqfp (uss-820td) symbol * type name/description 12v dda p 3.3 v power supply for analog pll. 2 3 xtal1 i crystal/clock input. if the internal oscillator is used, this is the crystal input. if an external oscillator is used, this is the clock input. 3 4 xtal2 o crystal/clock output. if the internal oscillator is used, this is the crystal output. if an external oscillator is used, this output should be left unconnected. 45v ddt p 3.3 v power supply for usb transceiver. 5 6 dmns i/o usb differential data bus minus. 6 7 dpls i/o usb differential data bus plus. 78v sst p device ground for usb transceiver. 12, 11, 10, 9, 8 13, 12, 11, 10, 9 a[4:0] i address bus. this is the address bus for the controller to access the register set. 13 14 v ssx p device ground. for compatibility with uss-820 revision b, this pin can be connected to a controller address bit, as long as it is guaranteed to be equal to 0 during register accesses and meets all address pin timing requirements. 14, 20, 21, 22, 23, 24, 34, 40 15, 22, 23, 24, 25, 26, 37, 43 v ss0 , v ss1 , v ss2, v ssx p device ground. 15 16 dsa o data set available. indicates one or more receive data sets are valid, or one or more transmit data sets are empty (available). for compatibility with uss-820 revision b, this output is 3-stated if mcsr.bdfeat = 0. 18 19 usbr o usb reset detected. indicates a usb reset event has been detected on usb. this pin will remain asserted until the ssr.reset register bit is cleared by firmware. for compatibility with uss-820 revision b, this output is 3- stated if mcsr.bdfeat = 0. 16 1, 17, 20, 21, 27 nc ? ? no connect. 17, 44 18, 47 v dd0 , v dd1 p 3.3 v power supply. 19 48 dppu o dpls pull-up. can be used to supply power to the dpls 1.5 k ? pull-up resistor to allow firmware to simulate a device physical disconnect. this pin is directly controlled by the dpen register bit. 25 28 rwupn i remote wake-up (active-low). device is initiating a remote wake-up from a suspend condition. this input is ignored if scr register bit rwupe = 0. 26 29 suspn o suspend (active-low). usb suspend has been detected; chip has entered suspend (low power) mode. this pin is deasserted when a wake-up event is detected.
agere systems inc. 9 data sheet, rev. 4 june 2001 usb device controller USS-820D pin information (continued) table 2. pin descriptions (continued) * active-low signals within this document are indicated by an n following the symbol names. ? pins marked as nc must have no external connections, except where noted. register timing characteristics all register timing specifications assume a 100 pf load on the d[7:0] package pins and a 70 pf load on all other package pins. 44-pin mqfp (USS-820D) 48-pin tqfp (uss-820td) symbol * type name/description 27 30 irqn o interrupt (programmable active-low or active-high). an interrupt signal is sent to the controller whenever an event such as tx/rx done, suspend, resume, usbreset, or sof occurs. 28 31 sofn o start of frame (active-low). this signal is asserted low for eight t clk periods when an sof token is received. 29 32 reset i reset. when this signal is held high, all state machines and registers are set at the default state. 30 33 nc ? ? no connect. for compatibility with the uss-820 revision b, this pin can be connected to a 3 v or 5 v supply with no harmful effect. 31 34 iocsn i chip select (active-low). 32 35 wrn i control register write (active-low). 33 36 rdn i control register read (active-low). 35, 36, 37, 38, 39, 41, 42, 43 38, 39, 40, 41, 42, 44, 45, 46 d[7:0] i/o data bus. table 3. timing parameters symbol parameter min max unit t clk internal clock period ? 83.3 ns t rst reset assert time 500 ? ns
10 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register timing characteristics (continued) table 4. register access timing?special function register (sfr) read 5-5352 figure 6. register access timing?sfr read symbol parameter min max unit trdasu read address setup time (starts before the trailing edge of rdn or iocsn, whichever is first ) 60 ? ns trdahd read address hold (starts after the trailing edge of rdn or iocsn, whichever is first ): operational suspended ? 10 ? 1 ? ? ns ns trddv1, trddv2 read data valid (from the leading edge of rdn or iocsn or from address valid, whichever is last , to data valid): operational suspended ? ? 74 33 ns ns trddz read data to z state (starts after the trailing edge of rdn or iocsn, whichever is first ) 232ns trdrec recovery time between reads (from the trailing edge of rdn or iocsn, whichever is first , to the next leading edge of rdn or iocsn, whichever is last ) 23 ? ns trdrecrxd recovery time between consecutive rxdat reads (from the trailing edge of rdn or iocsn, whichever is first , to the next trailing edge of rdn or iocsn, whichever is first ) 86 ? ns trdpw minimum pulse width (from the leading edge of rdn or iocsn, whichever is last , to the trailing edge of rdn or iocsn, which- ever is first ) 23 ? ns trddv2 iocsn rdn a d trdrec trdpw trdasu trdahd trddv1 valid valid trddz valid high impedance valid trdrecrxd
agere systems inc. 11 data sheet, rev. 4 june 2001 usb device controller USS-820D register timing characteristics (continued) table 5. register access timing?special function register (sfr) write 5-5353 figure 7. register access timing?sfr write symbol parameter min unit twrasu write address setup time (starts before the trailing edge of wrn or iocsn, whichever is first ) 60 ns twrahd write address hold (starts after the trailing edge of wrn or iocsn, whichever is first ) ? 10 ns twrpw write minimum pulse width (from the leading edge of wrn or iocsn, whichever is last , to the trailing edge of wrn or iocsn, whichever is first ) 23 ns twrdsu write data setup (from data valid to the trailing edge of wrn or iocsn, whichever is first ) 60 ns twrdhd write data hold (from the trailing edge of wrn or iocsn, whichever is first , to data not valid) ? 10 ns twrrec recovery time between write attempts (from the trailing edge of wrn or iocsn, whichever is first , to the next leading edge of wrn or iocsn, whichever is last ) 23 ns twrrecc recovery time between write completes (from the trailing edge of wrn or iocsn, whichever is first , to the next trailing edge of wrn or iocsn, whichever is first ) 86 ns iocsn wrn a d twrrecc twrpw twrasu twrahd twrdsu valid valid valid valid twrdhd twrrec
12 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface the USS-820D is controlled through an asynchronous, read/write register interface. registers are addressed via the a[4:0] pins, and control is provided through the rdn, wrn, and iocsn pins. reserved bits of registers must always be written with 0. writing 1 to these bits may produce undefined results. these bits return undefined values when read. a register read is accomplished by placing the register address on the a bus and asserting the iocsn and rdn pins. after read data valid (trddv), the register data will appear on the d bus. a register write is accomplished by placing the register address on the a bus and the data to be written on the d bus, and asserting the iocsn and wrn pins. tables 6 and 7 show alphabetical and numerical listings of all the available special function registers (sfr) for the USS-820D. for reference purposes, an alphabetized list of sfr bit names is included in appendix a. tables 11? 38 provide details for each of the registers. some of these registers are replicated for each endpoint. the individ- ual, endpoint-specific register is selected by the epindex register. table 6. special function registers (by name) register description address table page dsav data set available 1dh 37 40 dsav1 data set available 1 1eh 38 40 epcon* * contains shared bits. see special firmware action for shared register bits section. ? indexed by epindex. endpoint control register 0bh ? 18 21 epindex endpoint index register 0ah 17 20 faddr function address register 10h 21 26 lock suspend power-off locking register 19h 33 38 mcsr miscellaneous control/status register 1ch 36 39 pend pend hardware status update register 1ah 34 38 rev hardware revision register 18h 32 37 rxcnth receive fifo byte-count high register 07h ? 27 31 rxcntl receive fifo byte-count low register 06h ? 27 31 rxcon receive fifo control register 08h ? 28 31 rxdat receive fifo data register 05h ? 26 30 rxflg receive fifo flag register 09h ? 29 33 rxstat* endpoint receive status register 0dh ? 20 24 sbi* serial bus interrupt register 14h 13 17 sbi1* serial bus interrupt register 1 15h 14 18 sbie serial bus interrupt enable register 16h 11 16 sbie1 serial bus interrupt enable register 1 17h 12 16 scr system control register 11h 30 36 scratch scratch firmware information register 1bh 35 38 sofh* start of frame high register 0fh 15 19 sofl* start of frame low register 0eh 16 20 ssr* system status register 12h 31 37 txcnth transmit fifo byte-count high register 02h ? 23 26 txcntl transmit fifo byte-count low register 01h ? 23 26 txcon usb transmit fifo control register 03h ? 24 27 txdat transmit fifo data register 00h ? 22 26 txflg transmit fifo flag register 04h ? 25 28 txstat endpoint transmit status register 0ch ? 19 22
agere systems inc. 13 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) * indexed by epindex. ? contains shared bits. see special firmware action for shared register bits section. table 7. special function registers (by address) address register description table page 00h* txdat transmit fifo data register 22 26 01h* txcntl transmit fifo byte-count low register 23 26 02h* txcnth transmit fifo byte-count high register 23 26 03h* txcon usb transmit fifo control register 24 27 04h* txflg transmit fifo flag register 25 28 05h* rxdat receive fifo data register 26 30 06h* rxcntl receive fifo byte-count low register 27 31 07h* rxcnth receive fifo byte-count high register 27 31 08h* rxcon receive fifo control register 28 31 09h* rxflg receive fifo flag register 29 33 0ah epindex endpoint index register 17 20 0bh* epcon ? endpoint control register 18 21 0ch* txstat endpoint transmit status register 19 22 0dh* rxstat ? endpoint receive status register 20 24 0eh sofl ? start of frame low register 16 20 0fh sofh ? start of frame high register 15 19 10h faddr function address register 21 26 11h scr system control register 30 36 12h ssr ? system status register 31 37 14h sbi ? serial bus interrupt register 13 17 15h sbi1 ? serial bus interrupt register 1 14 18 16h sbie serial bus interrupt enable register 11 16 17h sbie1 serial bus interrupt enable register 1 12 16 18h rev hardware revision register 32 37 19h lock suspend power-off locking register 33 38 1ah pend pend hardware status update register 34 38 1bh scratch scratch firmware information register 35 38 1ch mcsr miscellaneous control/status register 36 39 1dh dsav data set available 37 40 1eh dsav1 data set available 1 38 40
14 14 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) special firmware action for shared register bits since the USS-820D registers are not bit-addressable and contain several bits that may be written by either firmware or hardware (shared bits), special care must be taken to avoid incorrect behavior. in particular, firm- ware must be careful not to write a bit after hardware has updated the bit, but before firmware has recog- nized the hardware update of the bit. there are two general cases where this may occur: 1. direct collision?firmware does a read-modify-write sequence to update a register bit, but between the firmware read and firmware write, hardware updates the bit. for example, in dual-packet mode, hardware could update an sbi/sbi1 bit while firm- ware is simultaneously resetting the same sbi/sbi1 bit. this would cause firmware to miss the fact that a new transfer has completed. 2. indirect collision?firmware does a read-modify- write sequence to update a register bit, but between the firmware read and firmware write, hardware updates a different bit in the same register. for example, firmware could do a read-modify-write to update the sofodis bit of the sofh register, but at the same time, hardware could be updating the asof status bit. firmware would inadvertently reset the asof bit without being aware of the hard- ware update. these problems can be avoided through the use of the pend register, which can only be written by firmware. firmware must ensure that the pend register bit is set before writing any registers that contain shared bits. all shared register bits have two copies: a standard copy and a pended copy. the manner in which these register bits are updated varies depending on the value of the pend register bit, as described in table 8. the standard copy is the bit that is read and written during normal operation (pend = 0). while pend = 1, hard- ware updates only affect the pended copy, and firm- ware updates only affect the standard copy. when firmware resets the pend bit, the pended copies of the shared bits are used to update the standard copies of the shared bits as described in table 9. through these means, hardware updates during a firmware read- modify-write sequence will not be missed. firmware must execute the following sequence when processing a shared bit (to avoid the direct collision case), or when writing a bit which resides in a register that contains shared bits (to avoid the indirect collision case): set the pend bit. read the register with the shared bit [read]. if processing a shared bit, respond to the shared bit. for example, for an sbi/sbi1 bit, process any data sets present for that endpoint. update the bit [modify]. write the register with the shared bit with the modi- fied data [write]. reset the pend bit. when a data set is written to a receive fifo, that fifo?s sbi/sbi1 register bit will set. firmware must process the indicated receive data set and, in doing so, manage that fifo?s sbi/sbi1 bit according to the sequence described in this section. in dual-packet mode, it is possible that a second data set will be written to a receive fifo before firmware has completed processing of the initial data set. this second data set could have been written either before or after firmware set the pend bit to 1. therefore, firm- ware cannot determine whether or not this second receive done indication was saved in the pended copy of the sbi/sbi1 bit. because of this uncertainty, firm- ware must process all receive data sets which are present in the indicated fifo before resetting the pend bit to 0. if the receive done indication of the second data set was in fact saved in the pended sbi/ sbi1 register, then the standard copy of the sbi/sbi1 bit will be set when firmware resets the pend bit to 0. table 8. shared register bit update behavior (asof example) bit update behavior while pend = 0 update behavior while pend = 1 update behavior when firmware resets pend to 0 asof (standard copy) updated by hardware (firmware must not write this register) updated by firmware updated as docu- mented in table 9 asof (pended copy) not used updated by hardware no longer used
agere systems inc. 15 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) in this case, the sbi/sbi1 bit will be set even though there is no corresponding data set present in the receive fifo. therefore, firmware must be prepared to service a receive done interrupt where no data sets are present in the indicated fifo. table 9 shows the values loaded into each of the stan- dard copies of the shared register bits when firmware resets the pend register bit . the register bits that are only updated by firmware, but reside in registers with shared bits and must therefore be updated only while pend is set, are shown in table 10. firmware should attempt to minimize the period during which pend is set in order to minimize the distortion of the detection of hardware events. register reads with side effects in general, USS-820D register reads do not have side effects?they do not cause any device state to change. the following are exceptions to this rule: rxdat reads cause the internal rx fifo read pointer to change and possibly cause the rxflg.rxurf register bit to set. rxcnth/rxcntl reads while rxflg.rxfif = 00 cause the rxflg.rxurf register bit to set. lock reads restart the register unlock sequence after suspend (described in special action required by uss-820/uss-825 after suspend ?ap97- 058cmpr-04). any register reads during a register unlock sequence after suspend, other than the lock register, cause the unlock sequence to fail and require the sequence to be restarted. table 9. shared register update values when firmware resets pend register bit(s) update value sbi all bits set to 1 if standard copy = 1 or pended copy = 1. sbi1 all bits set to 1 if standard copy = 1 or pended copy = 1. rxstat rxsetup loaded with pended copy if usb action updated rxsetup while pend was set. rxstat edovw set to 1 if standard copy = 1 or pended copy = 1. epcon rxstl set to 1 if standard copy = 1 or pended copy = 1. sofh asof set to 1 if standard copy = 1 or pended copy = 1. sofh ts loaded with pended copy if usb sof was received while pend was set. sofl all bits loaded with pended copy if usb sof was received while pend was set. ssr reset set to 1 if standard copy = 1 or pended copy = 1. table 10. register bits only updated while pend is set register bit(s) rxstat rxseq epcon all bits except rxstl sofh sofie, sofodis ssr susppo, suspdis, resume, suspend
16 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) register descriptions table 11. serial bus interrupt enable register (sbie)?address: 16h; default: 0000 0000b this register enables and disables the receive and transmit done interrupts for function endpoints 0 through 3. * for all bits, a 1 indicates the interrupt is enabled and causes an interrupt to be signaled to the microcontroller. a 0 indica tes the associated interrupt source is disabled and cannot cause an interrupt. however, the interrupt bit?s value is still reflected in the sbi/sb i1 register. all of these bits can be read/written by firmware. table 12. serial bus interrupt enable register 1 (sbie1)?address: 17h; default: 0000 0000b this register enables and disables the receive and transmit done interrupts for function endpoints 4 through 7. * for all bits, a 1 indicates the interrupt is enabled and causes an interrupt to be signaled to the microcontroller. a 0 indica tes the associated interrupt source is disabled and cannot cause an interrupt. however, the interrupt bit?s value is still reflected in the sbi/sb i1 register. all of these bits can be read/written by firmware. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 frxie3 ftxie3 frxie2 ftxie2 frxie1 ftxie1 frxie0 ftxie0 r/w bit* symbol function/description 7frxie3 function receive interrupt enable 3. enables receive done interrupt for endpoint 3 (frxd3). 6 ftxie3 function transmit interrupt enable 3. enables transmit done interrupt for endpoint 3 (ftxd3). 5frxie2 function receive interrupt enable 2. enables receive done interrupt for endpoint 2 (frxd2). 4 ftxie2 function transmit interrupt enable 2. enables transmit done interrupt for endpoint 2 (ftxd2). 3frxie1 function receive interrupt enable 1. enables receive done interrupt for endpoint 1 (frxd1). 2 ftxie1 function transmit interrupt enable 1. enables transmit done interrupt for endpoint 1 (ftxd1). 1frxie0 function receive interrupt enable 0. enables receive done interrupt for endpoint 0 (frxd0). 0 ftxie0 function transmit interrupt enable 0. enables transmit done interrupt for endpoint 0 (ftxd0). bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 frxie7 ftxie7 frxie6 ftxie6 frxie5 ftxie5 frxie4 ftxie4 r/w bit* symbol function/description 7frxie7 function receive interrupt enable 7. enables receive done interrupt for endpoint 7 (frxd7). 6ftxie7 function transmit interrupt enable 7. enables transmit done interrupt for endpoint 7 (ftxd7). 5frxie6 function receive interrupt enable 6. enables receive done interrupt for endpoint 6 (frxd6). 4ftxie6 function transmit interrupt enable 6. enables transmit done interrupt for endpoint 6 (ftxd6). 3frxie5 function receive interrupt enable 5. enables receive done interrupt for endpoint 5 (frxd5). 2ftxie5 function transmit interrupt enable 5. enables transmit done interrupt for endpoint 5 (ftxd5). 1frxie4 function receive interrupt enable 4. enables receive done interrupt for endpoint 4 (frxd4). 0ftxie4 function transmit interrupt enable 4. enables transmit done interrupt for endpoint 4 (ftxd4).
agere systems inc. 17 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 13. serial bus interrupt register (sbi)?address: 14h; default: 0000 0000b this register contains the usb function?s transmit and receive done interrupt flags for nonisochronous endpoints. these bits are never set for isochronous endpoints. * s = shared bit. see special firmware action for shared register bits section. for all bits in the interrupt flag register, a 1 indicates that an interrupt is actively pending; a 0 indicates that the interrupt is not active. the interrupt status is shown regardless of the state of the corresponding interrupt enable bit in the sbie/sbie1. hardware can only set bits to 1. in normal operation, firmware should only clear bits to 0. firmware can also set the bits to 1 for test purposes. this allows the interrupt to be generated in firmware. a set receive bit indicates either that valid data is waiting to be serviced in the rx fifo for the indicated endpoint and that the data was received without error and has been acknowledged, or that data was received with a receive data error requiring firmware intervention to be cleared. a set transmit bit indicates either that data has been transmitted from the tx fifo for the indicated endpoint and has been acknowledged by the host, or that data was transmitted with an error requiring firmware intervention to be cleared. if txnake = 1, this also may indicate that a nak was sent to the host in response to an in packet that was received when txfif = 00. this condition also sets txvoid. this sbi/sbi1 setting will persist until firmware clears txvoid (or clears txnake). bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 frxd3 ftxd3 frxd2 ftxd2 frxd1 ftxd1 frxd0 ftxd0 r/w (s*) bit symbol function/description 7 frxd3 function receive done flag, endpoint 3. 6 ftxd3 function transmit done flag, endpoint 3. 5 frxd2 function receive done flag, endpoint 2. 4 ftxd2 function transmit done flag, endpoint 2. 3 frxd1 function receive done flag, endpoint 1. 2 ftxd1 function transmit done flag, endpoint 1. 1 frxd0 function receive done flag, endpoint 0. 0 ftxd0 function transmit done flag, endpoint 0.
18 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 14. serial bus interrupt 1 register (sbi1)?address: 15h; default: 0000 0000b this register contains the usb function?s transmit and receive done interrupt flags for nonisochronous endpoints. these bits are never set for isochronous endpoints. * s = shared bit. see special firmware action for shared register bits section. for all bits in the interrupt flag register, a 1 indicates that an interrupt is actively pending; a 0 indicates that the inter- rupt is not active. the interrupt status is shown regardless of the state of the corresponding interrupt enable bit in the sbie/sbie1. hardware can only set bits to 1. in normal operation, firmware should only clear bits to 0. firmware can also set the bits to 1 for test purposes. this allows the interrupt to be generated in firmware. a set receive bit indicates either that valid data is waiting to be serviced in the rx fifo for the indicated endpoint and that the data was received without error and has been acknowledged, or that data was received with a receive data error requiring firmware intervention to be cleared. a set transmit bit indicates either that data has been transmitted from the tx fifo for the indicated endpoint and has been acknowledged by the host, or that data was transmitted with an error requiring firmware intervention to be cleared. if txnake = 1, this also may indicate that a nak was sent to the host in response to an in packet that was received when txfif = 00. this condition also sets txvoid. this sbi/sbi1 setting will persist until firmware clears txvoid (or clears txnake). bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 frxd7 ftxd7 frxd6 ftxd6 frxd5 ftxd5 frxd4 ftxd4 r/w (s*) bit symbol function/description 7 frxd7 function receive done flag, endpoint 7. 6ftxd7 function transmit done flag, endpoint 7. 5 frxd6 function receive done flag, endpoint 6. 4ftxd6 function transmit done flag, endpoint 6. 3 frxd5 function receive done flag, endpoint 5. 2ftxd5 function transmit done flag, endpoint 5. 1 frxd4 function receive done flag, endpoint 4. 0ftxd4 function transmit done flag, endpoint 4.
agere systems inc. 19 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 15. start of frame high register (sofh)?address: 0fh; default: 0000 0000b this register contains isochronous data transfer enable and interrupt bits and the upper 3 bits of the 11-bit time stamp received from the host. * s = shared bit. p = pend must be set when writing this bit. see special firmware action for shared register bits section. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 sofack asof sofie ftlock sofodis ts10 ts9 ts8 r r/w (s*) r/w (p*) r r/w (p*) r/w (s*) bit symbol function/description 7sofack sof token received without error (read only) . when set, this bit signifies that the 11-bit time stamp stored in sofl and sofh is valid. this bit is updated every time an sof token is received from the usb bus, and it is cleared when an artificial sof is generated by the frame timer. this bit is set and cleared by hardware. 6 asof any start of frame. this bit is set by hardware to signify that a new frame has begun. the interrupt can result either from the reception of an actual sof packet or from an artificially generated sof from the frame timer. this interrupt is asserted in hardware even if the frame timer is not locked to the usb bus frame timing. when set, this bit indicates that either the actual sof packet was received or an artificial sof was generated by the frame timer. setting this bit to 1 by firmware has the same effect as when it is set by hardware. this bit must be cleared to 0 by firmware if sofodis = 1 or if mcsr.feat = 1. if sofodis and mcsr.feat = 0, this bit clears itself after one t clk , which requires the system to detect start of frame via the sofn device pin. this bit also serves as the sof interrupt flag. this interrupt is only asserted in hard- ware if the sof interrupt is enabled (sofie set) and the interrupt channel is enabled. 5sofie sof interrupt enable . when set, setting the asof bit causes an interrupt request to be generated if the interrupt channel is enabled. hardware reads this bit but does not write to it. 4ftlock frame timer lock (read only) . when set, this bit signifies that the frame timer is presently locked to the usb bus frame time. when cleared, this bit indicates that the frame timer is attempting to synchronize the frame time. 3sofodis sof pin output disable . when set, no low pulse is driven to the sof pin in response to setting the asof bit. the sof pin is driven to 1 when sofodis is set. when this bit is clear, setting the asof bit causes the sof pin to be toggled with a low pulse for eight t clk periods. 2:0 ts[10:8] time stamp received from host . ts[10:8] are the upper 3 bits of the 11-bit frame number issued with an sof token. this time stamp is valid only if the sofack bit is set.
20 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 16. start of frame low register (sofl)?address: 0eh; default: 0000 0000b this register contains the lower 8 bits of the 11-bit time stamp received from the host. * s = shared bit. see special firmware action for shared register bits section. table 17. endpoint index register (epindex)?address: 0ah; default: 0000 0000b this register identifies the endpoint pair. the register?s contents select the transmit and receive fifo pair and serve as an index to endpoint-specific special function registers (sfrs). * the epindex register identifies the endpoint pair and selects the associated transmit and receive fifo pair. the value in thi s register plus sfr addresses select the associated band of endpoint-indexed sfrs (txdat, txcon, txflg, txcnth/l, rxdat, rxcon, rxflg, rxcnth/l, epcon, txstat, and rxstat). bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ts7 ts6 ts5 ts4 ts3 ts2 ts1 ts0 r/w (s*) bit symbol function/description 7:0 ts[7:0] time stamp received from host . this time stamp is valid only if the sofack bit in the sofh register is set. ts[7:0] are the lower 8 bits of the 11-bit frame number issued with an sof token. the time stamp remains at its previous value if an artificial sof is generated, and it is up to firmware to update it. these bits are set and cleared by hardware. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ? epinx2 epinx1 epinx0 ?r/w bit symbol function/description 7:3 ? reserved. write 0s to these bits. reads always return 0s. 2:0 epinx[2:0] endpoint index. epindex * function endpoint 0000 0000 function endpoint 0 0000 0001 function endpoint 1 0000 0010 function endpoint 2 0000 0011 function endpoint 3 0000 0100 function endpoint 4 0000 0101 function endpoint 5 0000 0110 function endpoint 6 0000 0111 function endpoint 7 the epindex register must not be changed during a sequence of rxdat reads of a particular data set. see the receive fifo section for more details.
agere systems inc. 21 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 18. endpoint control register (epcon)?address: 0bh; default: endpoint 0 = 0011 0101b; others = 0001 0000b this sfr configures the operation of the endpoint specified by epindex. this register is endpoint indexed. * s = shared bit. p = pend must be set when writing this bit. see special firmware action for shared register bits section. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxstl txstl ctlep rxspm rxie rxepen txoe txepen r/w (s*) r/w(p*) bit symbol function/description 7rxstl stall receive endpoint . when set, this bit stalls the receive endpoint. firmware must clear this bit only after the host has intervened through commands sent down endpoint 0. when this bit is set and rxsetup is clear, the receive endpoint responds with a stall handshake to a valid out token. when this bit is set and rxsetup is set, the receive endpoint will nack. this bit does not affect the reception of setup tokens by a control endpoint. this bit is set by the hardware if the data phase of the status stage of a control transfer does not use the correct data pid (data1) or has more than 0 data bytes. 6txstl stall transmit endpoint . when set, this bit stalls the transmit endpoint. firmware must clear this bit only after the host has intervened through commands sent down endpoint 0. when this bit is set and rxsetup is clear, the transmit endpoint responds with a stall handshake to a valid in token. when this bit is set and rxsetup is set, the receive endpoint will nack. 5ctlep control endpoint . when set, this bit configures the endpoint as a control endpoint. only control endpoints are capable of receiving setup tokens. 4 rxspm receive single-packet mode . when set, this bit configures the receive endpoint for single data packet operation. when enabled, only a single data packet is allowed to reside in the receive fifo. note: for control endpoints (ctlep = 1), this bit should be set for single-packet mode operation as the recommended firmware model. however, it is possible to have a control endpoint configured in dual-packet mode as long as the firm- ware handles the endpoint correctly. 3rxie receive input enable . when set, this bit enables data from the usb to be written into the receive fifo. if cleared, the endpoint responds to an out token by ignoring the data and returning a nack handshake to the host (unless rxstl is set, in which case a stall is returned). this bit does not affect a valid setup token. 2 rxepen receive endpoint enable . when set, this bit enables the receive endpoint. when disabled, the endpoint does not respond to a valid out or setup token. this bit is hardware read only and has the highest priority among rxie and rxstl. note: endpoint 0 is enabled for reception upon reset. 1txoe transmit output enable . when set, this bit enables the data in txdat to be trans- mitted. if cleared, the endpoint returns a nack handshake to a valid in token if the txstl bit is not set. 0 txepen transmit endpoint enable . when set, this bit enables the transmit endpoint. when disabled, the endpoint does not respond to a valid in token. this bit is hardware read only. note: endpoint 0 is enabled for transmission upon reset.
22 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 19. endpoint transmit status register (txstat)?address: 0ch; default: 0000 0000b this register contains the current endpoint status of the transmit fifo specified by epindex. this register is endpoint indexed. * for normal operation, this bit should not be modified by the user except as required by the implementation of usb standard com mands, such as set_configuration, set_interface, and clear_feature [stall]. the sie handles all sequence bit tracking required by normal usb traffic, as documented in the usb specification, section 8.6. ? only writable if txnake = 1. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 txseq txdsam txnake txflush txsovw txvoid txerr txack r/w* r/w r/w r w* r/w ? r bit symbol function/description 7 txseq transmitter current sequence bit (read, conditional write). * this bit is trans- mitted in the next pid and toggled on a valid ack handshake. this bit is toggled by hardware on a valid setup token. this bit can be written by firmware if the txsovw bit is set when written together with the next txseq value. 6 txdsam transmit data-set-available mode. if set, a nak response to an in token causes the corresponding rxav/txav bit in the dsav register to set, and the dsa output pin to assert (if enabled by mcsr.bdfeat), rather than the standard condition (transmit data set empty). this only occurs on naks caused by txfif = 00. this bit must not be set for isochronous endpoints. when reset to 0 (along with mcsr.feat, mcsr.bdfeat, and txstat.txnake), the device will behave like revision b. 5 txnake transmit nak mode enable. if set, a nak response to an in token causes the txvoid bit and the corresponding bits in the sbi/sbi1 register to set, causing an irqn interrupt (if enabled). this only occurs on naks caused by txfif = 00. this bit must not be set for isochronous endpoints. when set this bit also changes the meaning and usage of the txstat.txvoid bit. when reset to 0 (along with mcsr.feat, mcsr.bdfeat, and txstat.txdsam), the device will behave like revision b. 4txflush transmit fifo packet flushed (read only). updated at each sof. when set, this bit indicates that hardware flushed a stale isochronous data packet from the transmit fifo at sof. behavior when mcsr.feat = 0: to guard against a missed in token in isochronous mode, if, with txfif[1:0] = 11, no in token is received for the current endpoint, hardware automatically flushes the oldest packet and decrements the txfif[1:0] value. this flush does not occur if there is only one data set present (txfif = 01/10). behavior when mcsr.feat = 1: a firmware data set write causes a txfif bit to set. for isochronous endpoints, this data set does not become visible to the host until the next sof. the data set is intended to be read out during that frame. if that read does not occur (possibly due to a lost in packet), that data set is flushed at the next sof, setting txflush. if firmware writes two data sets during a single frame (txfif must have equalled 00 at the start of that frame), the first, older data set written is flushed at the subse- quent sof, setting txflush.
agere systems inc. 23 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 19. endpoint transmit status register (txstat)?address: 0ch; default: 0000 0000b (continued) * for normal operation, this bit should not be modified by the user except as required by the implementation of usb standard com mands, such as set_configuration, set_interface, and clear_feature [stall]. the sie handles all sequence bit tracking required by normal usb traffic, as documented in the usb specification, section 8.6. ? only writable if txnake = 1. bit symbol function/description 3txsovw transmit data sequence overwrite bit. * writing a 1 to this bit allows the value of the txseq bit to be overwritten. writing a 0 to this bit has no effect on txseq. this bit always returns 0 when read. 2txvoid transmit void. ? behavior when txnake = 0: this bit is read only if txnake = 0. indicates a void condition has occurred in response to a valid in token. transmit void is closely associated with the nack/ stall handshake returned by the function after a valid in token. this void condi- tion occurs when the endpoint output is disabled (txoe = 0) or stalled (txstl = 1), the corresponding receive fifo contains a setup packet (rxsetup = 1), the fifo contains no valid data sets (txfif = 00), or there is an existing fifo error (txurf = 1 or txovf = 1). this bit is used to check any nack/stall handshake returned by the function. this bit does not affect the ftxdx, txerr, or txack bits. this bit is updated by hardware at the end of a nonisochronous transaction in response to a valid in token. for isochronous transactions, this bit is not updated until the next sof. this bit is not updated at sof if txflush is performed. behavior when txnake = 1: when txnake = 1, this bit becomes writable by firmware. the meaning of the bit is also changed, to indicate only that a nak was sent to the host in response to an in when txfif = 00. hardware setting of this bit always takes priority over firm- ware writes. hardware setting of this bit also causes the corresponding sbi/sbi1 bit to set, possibly causing an interrupt. that setting will persist until txvoid is cleared by firmware. 1txerr transmit error (read only). indicates an error condition has occurred with the transmission. complete or partial data has been transmitted. the error can be one of the following: 1. data transmitted successfully but no handshake received. 2. transmit fifo goes into underrun condition while transmitting. these conditions also cause the corresponding transmit done bit, ftxdx in sbi or sbi1, to be set. for nonisochronous transactions, txerr is updated by hardware along with the txack bit at the end of data transmission. texerr and txack are updated at the same time?one bit is set to 1, and the other is reset to 0. for isochro- nous transactions, txerr is not updated until the next sof. this bit is not updated at sof if txflush is performed. 0txack transmit acknowledge (read only). indicates data transmission completed and acknowledged successfully. this condition also causes the corresponding transmit done bit, ftxdx in sbi or sbi1, to be set. for nonisochronous transactions, txack is updated by hardware along with the txerr bit at the end of data transmission. texerr and txack are updated at the same time?one bit is set to 1, and the other is reset to 0. for isochronous transactions, txack is not updated until the next sof. this bit is not updated at sof if txflush is performed.
24 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 20. endpoint receive status register (rxstat)?address: 0dh; default: 0000 0000b this register contains the current endpoint status of the receive fifo specified by epindex. this register is an endpoint-indexed sfr. * for normal operation, this bit should not be modified by the user except as required by the implementation of usb standard co mmands, such as set_configuration, set_interface, and clear_feature [stall]. the sie handles all sequence bit tracking required by normal usb traffic, as documented in the usb specification, section 8.6. ? s = shared bit. p = pend must be set when writing this bit. see special firmware action for shared register bits section. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxseq rxsetup stovw edovw rxsovw rxvoid rxerr rxack r/w* (p ? ) r/w (s ? )r r/w (s ? )w (p ? )r bit symbol function/description 7 rxseq receiver endpoint sequence bit (read, conditional write). * this bit is toggled on completion of an ack handshake in response to an out token. this bit is set (or cleared) by hardware after reception of a setup token. if the rxsovw bit is set, this bit can be written by firmware when written along with the new rxseq value. note: always verify this bit after writing to ensure that there is no conflict with hardware, which may occur if a new setup token is received. 6 rxsetup received setup token . this bit is set by hardware when a valid setup token has been received. when set, this bit causes received in or out tokens to be nacked until the bit is cleared to allow proper data management for the transmit and receive fifos from the previous transaction. in or out tokens are nacked even if the endpoint is stalled (rxstl or txstl) to allow a control transaction to clear a stalled endpoint. firmware must clear this bit after it has finished reading out the setup packet and is prepared for the next stage of the control transaction (data or status). for a stalled con- trol endpoint, this bit should not be cleared until the rxstl/txstl bits have been cleared. 5stovw start overwrite flag (read only). this bit is set by hardware upon receipt of a setup token for any control endpoint to indicate that the receive fifo is being overwritten with new setup data. when set, the fifo state (rxfif and read pointer) resets and is locked for this endpoint until edovw is set. this prevents a prior, ongoing firmware read from corrupting the read pointer as the receive fifo is being cleared and new data is being written into it. this bit is cleared by hardware at the end of handshake phase transmission of the setup stage. this bit is used only for control endpoints. 4edovw end overwrite flag. this flag is set by hardware during the handshake phase of a setup stage. it is set after every setup packet is received and must be cleared prior to reading the contents of the fifo. when set, the fifo state (rxfif and read pointer) remains locked for this endpoint until this bit is cleared. this prevents a prior, ongoing firmware read from corrupting the read pointer after the new data has been written into the receive fifo. this bit is used only for control endpoints. 3rxsovw receive data sequence overwrite bit. * writing a 1 to this bit allows the value of the rxseq bit to be overwritten. writing a 0 to this bit has no effect on rxseq. this bit always returns 0 when read.
agere systems inc. 25 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 20. endpoint receive status register (rxstat)?address: 0dh; default: 0000 0000b (continued) bit symbol function/description 2rxvoid receive void (read only). indicates a void condition has occurred in response to a valid out token. receive void is closely associated with the nack/stall handshake returned by the function after a valid out token. this void condition occurs when the endpoint input is disabled (rxie = 0) or stalled (rxstl = 1), the fifo contains a setup packet (rxsetup = 1), the fifo has no available data sets (rxfif = 11, or rxfif = 01/10 and rxspm = 1), or there is an existing fifo error (rxurf = 1 or rxovf = 1). this bit is set and cleared by hardware. for nonisochronous transactions, this bit is updated by hardware at the end of the transaction in response to a valid out token. for isochronous transactions, it is not updated until the next sof. 1rxerr receive error (read only). set when an error condition has occurred with the recep- tion of a setup or out transaction. complete or partial data has been written into the receive fifo. no handshake is returned. the error can be one of the following: 1. data failed crc check. 2. bit stuffing error. 3. a receive fifo goes into overrun or underrun condition while receiving. this bit is updated by hardware at the end of a valid setup or out token transaction (nonisochronous) or at the next sof on each valid out token transaction (isochro- nous). these conditions also cause the corresponding frxdx bit of sbi or sbi1 to be set. rxerr is updated with the rxack bit at the end of data reception. rxerr and rxack are updated at the same time?one bit is set to 1, and the other is reset to 0. 0rxack receive acknowledge (read only). this bit is set when an ack handshake is sent in response to data being written to the receive fifo. this read-only bit is updated by hardware at the end of a valid setup or out token transaction (nonisochronous) or at the next sof on each valid out token transaction (isochronous). this condition also causes the corresponding frxdx bit of sbi or sbi1 to be set. rxack is updated with the rxerr bit at the end of data reception. rxerr and rxack are updated at the same time?one bit is set to 1, and the other is reset to 0.
26 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 21. function address register (faddr)?address: 10h; default: 0000 0000b this sfr holds the address for the usb function. during bus enumeration, it is written by firmware with a unique value assigned by the host. if mcsr.feat = 1, this register is reset to 0 if a usb reset is detected. table 22. transmit fifo data register (txdat)?address: 00h; default: 0000 0000b data to be transmitted by the fifo specified by epindex is first written to this register. this register is endpoint indexed. txdat must not be written if txfif = 11. table 23. transmit fifo byte-count high and low registers (txcnth, txcntl)?address: txcnth = 02h, txcntl = 01h; default: txcnth = 0000 0000b; txcntl = 0000 0000b written by firmware to indicate the number of bytes just written to the transmit fifo specified by epindex. this register is endpoint indexed. txcntl should be written after txcnth. txcntl write increments txfif, vali- dating the data set just written. note: to send a status stage after a control write, no data control command, or a null packet, write 0 to txcnt. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ?a6a5a4a3a2a1a0 ?r/w bit symbol function/description 7? reserved. write 0 to this bit. reads always return 0. 6:0 a[6:0] 7-bit programmable function address. this register is written by firmware as a result of commands received via endpoint 0. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 txdat7 txdat6 txdat5 txdat4 txdat3 txdat2 txdat1 txdat0 w bit symbol function/description 7:0 txdat[7:0 ] transmit data byte (write only). to write data to the transmit fifo, write to this register. the write pointer is incremented automatically after a write. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 ?bc9bc8 ?r/w bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 bc7 bc6 bc5 bc4 bc3 bc2 bc1 bc0 r/w bit symbol function/description 15:10 ? reserved. write 0s to these bits. reads always return 0s. 9:0 bc[9:0] transmit byte count (write, conditional read). 10-bit, ring buffer. these bits store transmit byte count (txcnt).
agere systems inc. 27 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 24. usb transmit fifo control register (txcon)?address: 03h; default: 0000 0100b this register controls the transmit fifo specified by epindex. this register is endpoint indexed. * assumes mcsr.feat = 1. if mcsr.feat = 0, these ffsz settings indicate 64 bytes. ? atm mode is recommended for normal operation. advrm and revrp, which control the read marker and read pointer when atm = 0, ar e used for test purposes. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 txclr ffsz1 ffsz0 ? txiso atm advrm revrp r/w ? r/w bit symbol function/description 7txclr transmit fifo clear. setting this bit flushes the transmit fifo, resets all the read/write pointers and markers, resets the txcnth and txcntl registers, resets the txflush, txvoid, txerr, and txack bits of the txstat register, sets the txemp bit in txflg, and clears all other bits in txflg. hardware clears this bit after the flush. setting this bit does not affect the txseq bit in the txstat register. this bit should only be set when the endpoint is known to be inactive or there is a fifo error present. 6:5 ffsz[1:0] fifo size. these bits select the size of the transmit fifo. ffsz[1:0] nonisochronous size isochronous size 00 16 64 01 64 256 10 8* 512 11 32* 1024 4? reserved. write 0 to this bit. reads always return 0. 3txiso transmit isochronous data. firmware sets this bit to indicate that the transmit fifo contains isochronous data. the sie uses this bit to determine if a handshake is required at the end of a transmission. 2atm automatic transmit management. ? setting this bit (the default value) causes the read pointer and read marker to be adjusted automatically as indicated: status read pointer read marker ack unchanged advanced (1) nack reversed (2) unchanged 1. to origin of next data set. 2. to origin of the data set last read. this bit should always be set, except for test purposes. setting this bit disables advrm and revrp. this bit can be set and cleared by firmware. hardware neither clears nor sets this bit. this bit must always be set for isochronous endpoints (txiso = 1). 1advrm advance read marker control (non-atm mode only). ? setting this bit prepares for the next packet transmission by advancing the read marker to the origin of the next data packet (the position of the read pointer). hardware clears this bit after the read marker is advanced. this bit is effective only when the revrp, atm, and txclr bits are clear. 0revrp reverse read pointer (non-atm mode only). ? in the case of a bad transmission, the same data stack may need to be available for retransmit. setting this bit reverses the read pointer to point to the origin of the last data set (the position of the read marker) so that the sie can reread the last set for retransmission. hardware clears this bit after the read pointer is reversed. this bit is effective only when the advrm, atm, and txclr bits are all clear.
28 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 25. transmit fifo flag register (txflg)?address: 04h; default: 0000 1000b these flags indicate the status of data packets in the transmit fifo specified by epindex. this register is endpoint indexed. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 txfif1 txfif0 ? txemp txfull txurf txovf r? rr/w bit symbol function/description 7:6 txfif[1:0] transmit fifo index flags (read only). these flags indicate which data sets are present in the transmit fifo (see below). data sets present txfif[1:0] ds1 ds0 status 00 no no empty 01 no yes 1 set 10 yes no 1 set 11 yes yes 2 sets the txfif bits are set in sequence after each write to txcnt to reflect the addition of a data set. likewise, the txfif1 and tfif0 are cleared in sequence after each advance of the read marker to indicate that the set is effectively discarded. the bit is cleared whether the read marker is advanced by firmware (setting advrm) or automatically by hardware (atm = 1). the next-state table for the txfif bits is shown below: txfif[1:0] operation next txfif[1:0] 00 write txcnt 01 01 write txcnt 11 10 write txcnt 11 11 write txcnt 11 (txovf = 1) 00 advance read marker 00 01 advance read marker 00 11 advance read marker 10/01 10 advance read marker 00 xx reverse read pointer unchanged in isochronous mode, txovf, txurf, and txfif are handled using the following rule: firmware events cause status change immediately, while usb events cause status change only at sof. txfif is incremented by firmware and decremented by the usb. therefore, writes to txcnt increment txfif immediately. however, a successful usb transaction any time within a frame decrements txfif only at sof. the txfif flags must be checked before and after writes to the transmit fifo and txcnt for traceability. see the txflush bit in txstat. if mcsr.feat = 0: txfif bits are immediately visible to the host after a firmware write?the device will send the indicated data set(s) to the host in response to an in.
agere systems inc. 29 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 25. transmit fifo flag register (txflg)?address: 04h; default: 0000 1000b (continued) bit symbol function/description 7:6 txfif[1:0] transmit fifo index flags (read only) (continued). if mcsr.feat = 1: txfif bits are not visible to the host until the first sof is written, which occurs after the data set. prior to that sof, the device will return a zero-length data set in response to an in (unless there is another, older data set present from the prior frame). this ensures that a given data set may only be sent during the subsequent frame, as required by the usb specification. this behavior also allows firmware to occasionally be late in writing a data set (write complete after sof), without losing frame/data synchronization with the host. the late data set write will cause a zero-length data set to be sent to the host during the intended frame. the late set will be flushed at the end of the next frame, assuming firmware also writes the correct data set during that frame (see txstat.txflush description). firmware must not be late on consecutive frames (this will cause a loss of frame/data synchronization with the host), data sets may be sent during the wrong frame. note: firmware can enforce single-packet mode by only writing a new data set to the transmit fifo if there are currently no data sets present in the fifo (txfif = 00). to simplify firmware development, configure control endpoints in single-packet mode. 5:4 ? reserved. write 0s to these bits. reads always return 0s. 3txemp transmit fifo empty flag (read only). hardware sets this bit when firmware has not yet written any data bytes to the current fifo data set being written. hardware clears this bit when the empty condition no longer exists. this bit always tracks the current transmit fifo status regardless of isochronous or nonisochronous mode. 2txfull transmit fifo full flag (read only). hardware sets this bit when the number of bytes that firmware writes to the current transmit fifo data set equals the fifo size. hardware clears this bit when the full condition no longer exists. this bit always tracks the current transmit fifo status regardless of isochronous or nonisochronous mode. check this bit to avoid causing a txovf condition. 1txurf transmit fifo underrun flag (read, clear only). hardware sets this flag when a read is attempted from an empty transmit fifo. (this is caused when the value written to txcnt is greater than the number of bytes written to txdat.) this bit must be cleared by firmware through txclr. when this flag is set, the fifo is in an unknown state; there- fore, it is recommended that the fifo is reset in the error management routine using the txclr bit in txcon. when the transmit fifo underruns, the read pointer does not advance; it remains locked in the empty position. when this bit is set, all transmissions are nacked. in isochronous mode, txovf, txurf, and txfif are handled using the following rule: firmware events cause status change immediately, while usb events cause status change only at sof. since underrun can only be caused by usb, txurf is updated at the next sof regardless of where the underrun occurs in the frame.
30 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 25. transmit fifo flag register (txflg)?address: 04h; default: 0000 1000b (continued) table 26. receive fifo data register (rxdat)?address: 05h; default: 0000 0000b receive fifo data specified by epindex is stored and read from this register. this register is endpoint indexed. bit symbol function/description 0txovf transmit fifo overrun flag (read, clear only). this bit is set when an additional byte is written to a full fifo, or txcnt is written while txfif[1:0] = 11. this bit must be cleared by firmware through txclr. when this bit is set, the fifo is in an unknown state; thus, it is recommended that the fifo is reset in the error management routine using the txclr bit in txcon. when the transmit fifo overruns, the write pointer does not advance; it remains locked in the full position. check this bit after loading the fifo prior to writing the byte count register. when this bit is set, all transmissions are nacked. in isochronous mode, txovf, txurf, and txfif are handled using the following rule: firmware events cause status change immediately, while usb events cause status change only at sof. since overrun can only be caused by firmware, txovf is updated immedi- ately. check the txovf flag after writing to the transmit fifo before writing to txcnt. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxdat[7:0] r bit symbol function/description 7:0 rxdat[7:0] receive fifo data register (read only). to write to the receive fifo, the sie writes to this register. to read data from the receive fifo, the cpu reads from this register. the write pointer and read pointer are incremented automatically after a write and read, respectively. the epindex register must not be changed during a sequence of rxdat reads of a particular data set. see the receive fifo section for more details.
agere systems inc. 31 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 27. receive fifo byte-count high and low registers (rxcnth, rxcntl)?address: rxcnth = 07h, rxcntl = 06h; default: rxcnth = 0000 0000b, rxcntl = 0000 0000b high and low registers are in a two-register ring buffer that is used to store the byte count for the data packets received in the receive fifo specified by epindex. these registers are endpoint indexed. table 28. receive fifo control register (rxcon)?address: 08h; default: 0000 0100b controls the receive fifo specified by epindex. this register is endpoint indexed. bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 ?bc9bc8 ?r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 bc7 bc6 bc5 bc4 bc3 bc2 bc1 bc0 r bit symbol function/description 15:10 ? reserved. write 0s to these bits. reads always return 0s. 9:0 bc[9:0] receive byte count (read only). 10-bit, ring buffer byte. stores receive byte count (rxcnt). bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxclr ffsz1 ffsz0 rxffrc rxiso arm advwm revwp r/w bit symbol function/description 7rxclr receive fifo clear. setting this bit flushes the receive fifo, resets all the read/write pointers and markers, resets the rxsetup, stovw, edovw, rxvoid, rxerr, and rxack bits of the rxstat register, sets the rxemp bit in rxflg register, and clears all other bits in rxflg register. hardware clears this bit when the flush operation is completed. setting this bit does not affect the rxseq bit of rxstat. this bit should only be set when the endpoint is disabled or there is a fifo error present. firmware should never set this bit to clear a setup packet. the next setup packet will automatically clear the receive fifo. 6:5 ffsz[1:0] fifo size. these bits select the size of the receive fifo. ffsz[1:0] nonisochronous size isochronous size 00 16 64 01 64 256 10 8* 512 11 32* 1024 * assumes mcsr.feat = 1. if mcsr.feat = 0, these ffsz settings indicate 64 bytes.
32 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 28. receive fifo control register (rxcon)?address: 08h; default: 0000 0100b (continued) bit symbol function/description 4 rxffrc fifo read complete. when set, the receive fifo is released when a data set read is complete. setting this bit clears the rxfif bit (in the rxflg register), corresponding to the data set that was just read. hardware clears this bit after the rxfif bit is cleared. all data from this data set must have been read. for isochronous endpoints, firmware must check rxflush before setting rxffrc, and the act of setting rxffrc clears rxflush. see rxflush description for details. note: fifo read complete only works if the stovw and edovw bits are both cleared. 3 rxiso receive isochronous data. when set, this indicates that the receive fifo is programmed to receive isochronous data and to set up the usb interface to handle an isochronous data transfer. 2arm auto receive management. * when set, the write pointer and write marker are adjusted automatically based on the following conditions: rx status write pointer write marker ack unchanged advanced nack reversed unchanged this bit should always be set, except for test purposes. when this bit is set, setting revwp or advwm has no effect. hardware neither clears nor sets this bit. this bit can be set and cleared by firmware. this bit must always be set for isochronous endpoints (rxiso = 1). 1advwm advance write marker (non-arm mode only). * when set, the write marker is advanced to the origin of the next data set. advancing the write marker is used for back-to-back receptions. hardware clears this bit after the write marker is advanced. setting this bit is effective only when the revwp, arm, and rxclr bits are clear. 0revwp reverse write pointer (non-arm mode only). * when set, the write pointer is returned to the origin of the last data set received, as identified by the write marker. the sie can then reread the last data packet and write to the receive fifo starting from the same origin when the host resends the same data packet. hardware clears this bit after the write pointer is reversed. setting this bit is effective only when the advwm, arm, and rxclr bits are clear. revwp is used when a data packet is bad. when the function interface receives the data packet again, the write starts at the origin of the previous (bad) data set. * arm mode is recommended for normal operation. advwm and revwp, which control the write marker and write pointer when arm = 0, are used for test purposes.
agere systems inc. 33 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 29. receive fifo flag register (rxflg)?address: 09h; default: 0000 1000b these flags indicate the status of the data packets in the receive fifo specified by epindex. this register is endpoint indexed. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxfif1 rxfif0 ? rxflush rxemp rxfull rxurf rxovf r?r r r/w bit symbol function/description 7:6 rxfif[1:0] receive fifo index flags (read only). these read-only flags indicate which data packets are present in the receive fifo (see below). data sets present rxfif[1:0] ds1 ds0 status 00 no no empty 01 no yes 1 set 10 yes no 1 set 11 yes yes 2 sets the rxfif bits are updated after each write to rxcnt to reflect the addition of a data packet. likewise, the rxfif bits are cleared in sequence after each setting of the rxffrc bit. the next-state table for rxfif bits is shown below for operation in dual- packet mode. rxfif[1:0] operation next rxfif[1:0] 00 advance write marker 01 01 advance write marker 11 10 advance write marker 11 11 advance write marker 11 not possible?device will nack any out. 00 set rxffrc 00 01 set rxffrc 00 11 set rxffrc 10/01 10 set rxffrc 00 00 reverse write pointer unchanged when the receive fifo is programmed to operate in single-packet mode (rxspm set in epcon), valid rxfif states are 00 and 01 only. in isochronous mode, rxovf, rxurf, and rxfif are handled using the following rule: firmware events cause status change immediately, while usb events cause status change only at sof. rxfif is incremented by the usb and decremented by firmware. therefore, setting rxffrc decrements rfif immediately. however, a successful usb transaction within a frame increments rxfif only at sof. if mcsr.feat = 1: an old data set is flushed from an isochronous fifo if it is not read out by firmware during the intended frame (see rxflg.rxflush description). this flush occurs at sof, sets rxflg.rxflush, and causes rxfif to decrement without firmware intervention.
34 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 29. receive fifo flag register (rxflg)?address: 09h; default: 0000 1000b (continued) bit symbol function/description 7:6 rxfif[1:0] receive fifo index flags (read only) (continued). for traceability, the rxfif flags must be checked before and after reads from the receive fifo and the setting of rxffrc in rxcon. note: to simplify firmware development, it is recommended that control endpoints are used in single-packet mode only. 5? reserved. write 0s to these bits. reads always return 0s. 4 rxflush receive fifo flush (read only). only available if mcsr.feat = 1. updated at every sof, and only used for isochronous endpoints. rxfif bits are set when valid data sets are received from the host. for isochronous endpoints, this rxfif increment does not occur until the next sof. during that subsequent frame, it is the responsibility of firmware to read out the data set. if that read is not completed (rxffrc set by firmware) by the time the next sof is received, that data set is flushed from the receive fifo?rxfif is decremented by hardware. this flush is indicated by hardware by setting the rxflush bit. while this bit is set, the affect of firmware receive fifo data (rxdat) reads is blocked, in order to stop potential corruption of a new data set. before firmware sets rxffrc (for isochronous endpoints only), it must first check rxflush. if rxflush is set, firmware must discard the data set which it just read, because it is potentially corrupted. this situation should only occur if firmware is late in reading out a data set (read not completed before sof). firmware must not be late on consecutive frames? this will cause a loss of frame/data synchronization with the host?data sets may be visible to firmware during the wrong frame. firmware must always set rxffrc at the end of a data set read, even if rxflush = 1. rxflush is reset to 0 by the setting of rxffrc to 1. 3rxemp receive fifo empty flag (read only). hardware sets this flag when there are no data bytes present in the data set currently being read. hardware clears the bit when the empty condition no longer exists. this bit always tracks the current status of the receive fifo, regardless of isochronous or nonisochronous mode. 2rxfull receive fifo full flag (read only). hardware sets this flag when the data set currently being read contains the same number of data bytes as the size of the fifo. hardware clears the bit when the full condition no longer exists. this bit always tracks the current status of the receive fifo regardless of isochronous or nonisochronous mode. 1 rxurf receive fifo underrun flag (read, clear only). hardware sets this bit when an addi- tional byte is read from an empty receive fifo or when rxcnth or rxcntl is read while rxfif[1:0] = 00. hardware does not clear this bit, so it must be cleared by firm- ware through rxclr. when the receive fifo underruns, the read pointer does not advance. it remains locked in the empty position. when this bit is set, all transmissions are nacked. in isochronous mode, rxovf, rxurf, and rxfif are handled using the following rule: firmware events cause status change immediately, while usb events cause status change only at sof. since underrun can only be caused by firmware, rxurf is updated immediately. the rxurf flag must be checked after reads from the receive fifo before setting the rxffrc bit in rxcon. note: when this bit is set, the fifo is in an unknown state. it is recommended that the fifo is reset in the error management routine using the rxclr bit in the rxcon register.
agere systems inc. 35 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 29. receive fifo flag register (rxflg)?address: 09h; default: 0000 1000b (continued) bit symbol function/description 0rxovf receive fifo overrun flag (read, clear only). this bit is set when the sie writes an additional byte to a full receive fifo or writes a byte count to rxcnt with rxfif[1:0] = 11. this bit must be cleared by firmware through rxclr, although it can be cleared by hardware if a setup packet is received after an rxovf error has already occurred. when this bit is set, all transmissions are nacked. in isochronous mode, rxovf, rxurf, and rxfif are handled using the following rule: firmware events cause status change immediately, while usb events cause status change only at sof. since overrrun can only be caused by the usb, rxovf is updated only at the next sof regardless of where the overrun occurred during the current frame. note: when this bit is set, the fifo is in an unknown state. it is recommended that the fifo is reset in the error management routine using the rxclr bit in the rxcon register. when the receive fifo overruns, the write pointer does not advance. it remains locked in the full position.
36 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 30. system control register (scr)?address: 11h; default: 0000 0000b this register controls the fifo mode, irq mask, and irq mode selection. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 irqpol rwupe ie_susp ie_reset sreset irqlvl t_irq ? r/w ? bit symbol function/description 7irqpol irq polarity. determines the polarity of the irqn output. when asserted, the irqn output is active-high (default is active-low). firmware must be careful to ensure that setting this bit does not cause a false interrupt to be detected and processed. 6rwupe enable remote wake-up feature. when set, remote wake-up is enabled. 5 ie_susp enable suspend interrupt. when set, the suspend interrupt is enabled. 4 ie_reset enable reset interrupt. when set, the reset interrupt is enabled. 3sreset software reset. setting this bit to 1 in software places the USS-820D in the reset state. this is equivalent to asserting the hardware reset pin, except that this feature is not available if the device is suspended. setting this bit back to 0 leaves the USS-820D in an unconfigured state that follows a hardware reset. if mcsr.feat = 1, ssr.suppo = 0 and mcsr.susploe = 0: this bit may also be set to 1 while the device is suspended. the effect of this write is to wake up the device as if a remote wake-up had been performed, with the following excep- tions: 1) resume signaling is not transmitted to the host, 2) the feature is enabled regard- less of the scr.rwupe setting, and 3) the mcsr.rwupr register bit does not set. the actual setting of the scr.sreset register bit does not occur until the device is resumed and internal clocks are enabled, but the wake-up is initiated immediately. once the wake-up is complete, the sreset bit sets, and the behavior is the same as if sreset had been set while the device was awake. since the host will still expect the device to be suspended, this feature should not be used with bus-powered devices, since the device will exceed the suspend power requirement. 2irqlvl interrupt mode. level mode interrupt is selected when this bit is cleared. pulse mode interrupt is selected when this bit is set. in pulse mode, irq signal is driven (high or low, depending on the irqpol setting) by USS-820D for two t clk periods. 1t_irq global interrupt enable. when this bit is set, it enables hardware interrupt to be generated on irq pin when any of tx/rx bits, asof bit, reset bit, or suspend bit is set. 0? reserved. write 0 to this bit. reads always return 0.
agere systems inc. 37 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 31. system status register (ssr)?address: 12h; default: 0000 0000b this register allows control and monitoring of the usb suspend and reset events. * s = shared bit. p = pend must be set when writing this bit. see special firmware action for shared register bits section. table 32. hardware revision register (rev)?address: 18h; default: 0001 0011b this register contains the hardware revision number, which will be incremented for each version of the hardware. this will allow firmware to query the hardware status and determine which functions or features are supported. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ? susppo suspdis resume suspend reset ? r/w (p*) r w (p*) r/w (s*) bit symbol function/description 7:5 ? reserved. write 0s to these bits. reads always return 0s. 4susppo suspend power off. this bit must be set by firmware if externally connected devices will be powered off during a suspend. the correct value of this bit must be established before firm- ware suspends the USS-820D and should only need to be done once at device initialization time. 3suspdis suspend disable. when asserted, this bit disables the detection of a usb suspend event. this bit is for test purposes and should not be set during normal system operation. 2resume resume detected. for a complete description of the use of this bit, see the suspend and resume behavior section of this document. when set, the USS-820D has detected and responded to a wake-up condition, either global or remote. a global resume is indicated when the host asserts a non-idle state on the usb bus. a remote wake-up is indicated when the device asserts the rwupn input pin (if that feature is enabled by the rwupe bit). this bit should be reset by firmware as soon as possible after resuming to allow the next suspend event to be detected. 1 suspend suspend detected (read only)/suspend control (write only). for a complete description of the use of this bit, see the suspend and resume behavior section of this document. this bit serves as both a read-only status bit and a write-only control bit. for this reason, firmware cannot do a simple read/modify/write sequence to update this register. firmware must always explicitly specify the correct value of this suspend control bit when writing ssr. the read- only status bit is set by hardware when a suspend condition is detected on the usb bus, and clears itself after the suspend condition ceases and the device resumes. the bit will remain set during device wake-up. the value of this read-only bit is not affected by firmware writes. the write-only control bit is only updated by firmware, and is used to suspend the device by setting the bit to 1, and then setting the bit to 0. this write sequence will cause the device to suspend regardless of the initial value of the bit, which cannot be read. 0 reset usb reset detected. when set, a reset condition is detected on the usb bus. if interrupt is enabled (t_irq and ie_reset set), an interrupt is generated to the controller. firmware clears this bit. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 main hardware revision number sub hardware revision number r bit symbol function/description 7:4 ? main hardware revision number. 3:0 ? sub hardware revision number.
38 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 33. suspend power-off locking register (lock)?address: 19h; default: 0000 0001b this register contains the control and status which enables the USS-820D locking mechanism. this feature protects the internal register set from being corrupted during and immediately after a suspend where the external controller is powered off. the feature is enabled by the susploe bit, and its proper usage is documented in the special action required by uss-820/uss-825 after suspend application note (ap97-058cmpr-04). table 34. pend hardware status update register (pend)?address: 1ah; default: 0000 0000b this register contains the pend bit. table 35. scratch firmware information register (scratch)?address: 1bh; default: 0000 0000b this register contains a 7-bit scratch field that can be used by firmware to save and restore information. one possible use would be to save the device?s usb state (e.g., default, addressed) during suspend power off. the register also contains the resume interrupt enable bit. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ?unlocked ?r/w bit symbol function/description 7:1 ? reserved. 0unlocked locking control/status. use of this bit is described in the special action required by uss-820/uss-825 after suspend application note (ap97-058cmpr-04). bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ?pend ?r/w bit symbol function/description 7:1 ? reserved. 0pend pend. when set, this bit modifies the behavior of other shared register bits. see the special firmware action for shared register bits section of this document for a detailed explanation. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ie_resume scratch r/w r/w bit symbol function/description 7ie_resume enable resume interrupt. when set, the resume interrupt is enabled. 6:0 scratch scratch information.
agere systems inc. 39 data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 36. miscellaneous control/status register (mcsr)?address: 1ch; default: 0000 0000b (44-pin mqfp?USS-820D) 0001 0000b (48-pin tqfp?uss-820td) this register contains miscellaneous control and status bits. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rwupr init susps pkgid feat bdfeat susploe dpen r r r r r/w r/w r/w r/w bit symbol function/description 7rwupr remote wake-up remember. this bit is only available if mcsr.feat = 1; otherwise, it always reads 0. updated by hardware on each wake-up from a suspended state. this bit is set to 1 if the wake-up was caused by a remote wake-up event (rwupn pin asserted). otherwise, it is reset to 0 (on a global resume or usb reset). if rwupn is asserted simultaneously with a global wake-up, the bit is reset to 0 (global wake-up wins). when set, this bit indicates that resume signaling will be transmitted upstream. 6init device initialized. this bit will read 0 until internal clocks are turned on after a hardware reset. this bit is not affected by software reset. this bit can be used by firmware to deter- mine when the device is operational after a hardware reset. 5susps suspend status. indicates the current suspended status of the device. this bit will be set when the device goes suspended and will remain set until internal clocks are turned back on at the end of a resume sequence. 4pkgid package identification. indicates the package type. this bit will read 0 for the 44-pin mqfp package (USS-820D) and 1 for the 48-pin tqfp package (uss-820td). this value is established at the end of a hardware reset sequence. 3feat feature enable. when set, this bit enables various features introduced in revision c of the uss-820c. this bit controls those features which do not impact existing circuit boards using the uss-820 revision b (i.e., those features not enabled by mcsr.bdfeat). these features are explained in detail in the appendix c of the data sheet. when reset to 0 (along with mcsr.bdfeat, txstat.txdsam and txstat.txnake), the device will behave like revision b. 2bdfeat board feature enable. when set, this bit enables various features introduced in revi- sion c of the uss-820c. this bit controls those features which could be incompatible with existing circuit boards using the uss-820 revision b. these features are explained in detail in appendix c of the data sheet. when reset to 0 (along with mcsr.feat, txstat.txdsam and txstat.txnake), the device will behave like revision b. 1susploe suspend lock out enable. enables the device locking mechanism, which will then engage on every device resume. the correct value of this bit must be established before firmware suspends the device. 0dpen dpls pull-up enable. controls the dppu output pin, which may be used to power the external dpls pull-up resistor. this can be used by firmware to make the device appear disconnected from the host without a physical disconnect. when dpen = 1, the dppu output pin is driven high. when dpen = 0, the dppu output pin is 3-stated.
40 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D register interface (continued) table 37. data set available (dsav)?address: 1dh; default: 0000 0000b this register contains receive/transmit data set available bits. table 38. data set available (dsav1)?address: 1eh; default: 0000 0000b this register contains receive/transmit data set available bits. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxav3 txav3 rxav2 txav2 rxav1 txav1 rxav0 txav0 rrrrrrrr bit symbol function/description 7rxav3 receive/transmit data set available. this feature is only available if mcsr.feat = 1 or txdsam = 1; otherwise, reads 0. may be used to improve firmware efficiency when polling endpoints. for receive fifos, this register indicates that one or more data sets are available to be read. for transmit fifos, this register indicates that one or more data sets are available to be written. bits always read 0 for endpoints which are not enabled (rxepen/txepen = 0). if a transmit endpoint has txdsam = 1, the corresponding rxav/txav bit of the dsav register indicates instead that the txvoid bit is set (a nak has been sent to the host). this usage when txdsam = 1 does not require mcsr.feat = 1. 6 txav3 5rxav2 4 txav2 3rxav1 2 txav1 1rxav0 0 txav0 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 rxav7 txav7 rxav6 txav6 rxav5 txav5 rxav4 txav4 rrrrrrrr bit symbol function/description 7rxav7 receive/transmit data set available. this feature is only available if mcsr.feat = 1 or txdsam = 1; otherwise, reads 0. may be used to improve firmware efficiency when polling endpoints. for receive fifos, this register indicates that one or more data sets are available to be read. for transmit fifos, this register indicates that one or more data sets are available to be written. bits always read 0 for endpoints which are not enabled (rxepen/txepen = 0). if a transmit endpoint has txdsam = 1, the corresponding rxav/txav bit of the dsav register indicates instead that the txvoid bit is set (a nak has been sent to the host). this usage when txdsam = 1 does not require mcsr.feat = 1. 6 txav7 5rxav6 4 txav6 3rxav5 2 txav5 1rxav4 0 txav4
agere systems inc. 41 data sheet, rev. 4 june 2001 usb device controller USS-820D interrupts figure 8 describes the device interrupt logic. each of the indicated usb events are logged in a status register bit. each status bit has a corresponding enable bit that allows the event to cause an interrupt. interrupts can be masked globally by the t_irq bit of the scr register. the active level and signaling mode (level vs. pulse) of the irqn output pin can be controlled by the irqpol and irqlvl bits of the scr register. all interrupts have equal priority?firmware establishes its own priority by the order in which it checks these status bits during interrupt processing. 5-6402 figure 8. USS-820D interrupts usb reset usb suspend ie_susp suspend usb resume ie_resume resume usb start of frame pseudo start of frame endpoint 7 receive complete sbie1[7] sbi1[7] endpoint 0 receive complete sbie[1] sbi[1] endpoint 7 transmit complete sbie1[6] sbi1[6] endpoint 0 transmit complete sbie[0] sbi[0] ie_reset reset sofie asof t_irq interrupt present rising edge detect & pulse generate irqlvl i o irqn pin irqpol
42 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D firmware responsibilities for usb setup commands all setup commands are passed through from the usb host to the corresponding receive fifo (assuming no data transfer errors). firmware must interpret and execute each command according to its usb definition. reception of a new setup command can be identified by the rxsetup bit being set when a receive interrupt is generated. any old data in the receive fifo is overwritten by a new setup command. the stovw register bit is set by hardware when a new setup packet is detected. when the complete setup packet has been written, hardware resets the stovw bit and sets the edovw bit. if either the stovw or edovw bit is set, the effect of any firmware actions on the fifo pointers is blocked. this prevents the fifo from underflowing as a result of firm- ware attempting to read the fifo while hardware is writing a new setup packet. firmware must reset the edovw bit, read the setup command from the fifo, and then check the stovw and edovw bits. if either is set, the setup that was just read out is old and should be discarded. firmware must then proceed with reading the new setup command. firmware responsibilities for interpreting and executing usb standard commands are defined in table 39. table 39. firmware responsibilities for usb setup commands usb command firmware responsibility get_status for device status, firmware should write two data bytes to transmit fifo 0, where bit 0 of byte 0 indicates if the device is self-powered, and bit 1 indicates if the remote wake-up feature is supported (which should equal the value stored in the rwupe register bit). for interface status, firmware should write two data bytes of zeros. for endpoint status, firmware should write two data bytes to transmit fifo 0, where bit 0 of byte 0 is the rxstl or txstl bit of the endpoint indicated by the setup command. set/clear_feature for the device_remote_wakeup feature, firmware should set/reset the rwupe register bit. for the endpoint_stall feature, firmware should set/clear the rxstl or txstl register bit indicated by the setup command. firmware must also handle all side effects of these commands as documented in the usb specification, such as zeroing an endpoint?s data toggle bit on clear_feature[stall]. set_address firmware should write the faddr register with the device address indicated by the setup command. this write must not occur until after the status stage of the control transfer has completed successfully. get_configuration, set_configuration, get_interface, set_interface firmware must maintain all information regarding which endpoints, interfaces, alter- nate settings, and configurations are supported and/or currently enabled. the enabled status of a particular endpoint direction, as specified by the current configu- ration, interface, and alternate setting, must be indicated in the corresponding rxepen or txepen register bit. firmware must also handle any side effects of these commands as documented in the usb specification, such as zeroing an endpoint?s stall and data toggle bits on set_interface or set_configuration. get_descriptor, set_descriptor firmware must maintain all information regarding all types of descriptors and write the appropriate descriptor information to transmit fifo 0 upon receiving get_descriptor, or read the appropriate descriptor information from receive fifo 0 upon receiving set_descriptor.
agere systems inc. 43 data sheet, rev. 4 june 2001 usb device controller USS-820D firmware responsibilities for usb setup commands (continued) firmware must keep track of the direction of data flow during a control transfer, and detect the start of the status stage by a change in that direction. for control out transfers, the status stage will be an in, and the firmware should write a zero-byte data packet to the transmit fifo, assuming the command completed successfully. for control in transfers, the status stage will be an out, and the firmware should read the data packet and set the rxffrc register bit (like any other out transfer), again assuming the command completed successfully. this will cause an ack to be sent to the host, indicating a successful completion. firmware should stall endpoint 0 if it receives a stan- dard command that does not match any of the defined commands or a valid command that contains a param- eter with a bad value (e.g., get_status[endpoint x] when endpoint x is not enabled). firmware should also stall if the data stage of a control transaction attempts to transfer more bytes than were indicated by the setup stage. firmware must interpret any vendor or class commands as defined by the application. other firmware responsibilities frame timer behavior the USS-820D contains an internal frame timer that allows the device to lock to the usb host frame timer, and to synthesize lost sof packets, as required by the usb specification. the frame timer requires three valid sof packets from the host in order to lock to the host frame timer. this locked status is indicated by the ftlock status bit in sofh. in order to achieve this lock, the interval between each sof must be within 45 clocks of the nominal 12,000 clocks, and the successive intervals must be within two clocks of each other. both of these conditions will be true in a correctly functioning system with no bus errors. while the frame timer is locked, it will synthesize sofs by setting asof, generating an sof interrupt (if sofie = 1), and asserting the sofn pin (if sofodis = 0) for up to three consecutive frames if sof packets are no longer received from the host. the frame timer will become unlocked under any of the following conditions: hard or soft reset. usb reset. the device goes suspended. no sof packets are received from the host for three frames. an sof is received that violates the usb specifica- tion for frame interval or previous frame length com- parison. suspend and resume behavior note: in the following sections describing suspend and resume behavior, the following terminology is used: device?the entire product that contains the uss- 820d, such as a modem or printer. application?all electronic components of the device other than the USS-820D, such as a microcontroller, ram, power control logic, reset logic, or crystal. firmware?code running on the microcontroller which is part of the application. controller?that intelligent part of the application which uses the USS-820D address, data and read/ write pins to access its internal registers. powered-off components?those parts of the appli- cation which are connected to the USS-820D and powered off during suspend, for example, a micro- controller or ram. hardware?logic inside the USS-820D. table 40. other firmware responsibilities usb event firmware responsibility usb reset usb reset can be detected by reading a 1 from the reset bit of the ssr register. if the usb interrupt is enabled (ie_reset), this will be indicated by the irqn output. at that time, firmware must reset any information it maintains regarding endpoints, interfaces, alter- nate settings, and configurations. all rxepen and txepen endpoints should be set to 0, except for endpoint 0, which should be set to 1. the function address register faddr should be set to 0. the data toggle bits for all endpoints should be set to 0 as well. if mcsr.feat = 1, faddr is automati- cally cleared to 0 when usb reset is detected. usb suspend and resume firmware must manage the suspend and resume register bits, as docu- mented in the following section, in order to meet the usb specifications for bus- powered devices.
44 44 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D suspend and resume behavior (continued) during a suspend/resume sequence, the following sequence of events occurs: 1. hardware suspend detect: the USS-820D detects a suspend request from the host on usb and noti- fies firmware. 2. firmware suspend initiate: firmware reacts to the pending suspend request and suspends the device. 3. hardware resume detect/initiate: some time later a resume is initiated, either by the host or the appli- cation. 4. hardware resume sequence: when the resume is complete, the USS-820D notifies firmware. 5. firmware resume sequence: firmware reacts to the resume and completes any required actions. the following sections describe each of these steps in more detail. hardware suspend detect the USS-820D detects a usb suspend condition if a j state persists on the bus for at least 3 ms. when this suspend condition is detected, hardware sets the ssr.suspend register status bit and, if ie_susp = 1, causes an interrupt. suspend detection may be blocked by firmware by setting the ssr.suspdis register bit to 1. ssr.suspdis should only be set for test purposes, never in a running system. firmware suspend initiate when firmware detects that a suspend request from the host has been detected, it must prepare itself, and any other application components for which it is responsible, for suspend mode. for bus-powered devices, this will normally require turning off power to application components or placing them in low-power mode. when firmware is finished preparing for a device suspend, it should check the ssr.suspend register status bit once more. if this status bit has reset, firm- ware should abort the suspend sequence, since the host has already awakened the device. this will only happen if firmware is too slow in responding to the suspend detect. if the status bit is still set, firmware should proceed with the suspend sequence. this second check of the status bit guarantees that the device will see wake-up signaling of sufficient length from the host. to suspend the USS-820D, firmware must set the ssr.suspend register control bit to 1, and then reset the bit to 0. this action causes to the USS-820D to immediately enter suspend mode. in order to guarantee correct behavior when resuming, firmware must not attempt any register reads until at least three trdrec periods have elapsed since reset- ting the ssr.suspend register control bit. since firmware must have the pend register bit set when modifying the ssr.suspend register bit, and since registers cannot be written while the USS-820D is suspended, firmware must remember to reset the pend register bit after the USS-820D resumes. since the ssr.suspend register status bit will remain set while the USS-820D is suspended, a pending suspend interrupt will remain until the USS-820D resumes. for this reason, firmware may wish to reset the scr.ie_susp bit before suspending the uss- 820d. in order to meet the usb specification?s current draw limit for suspended devices, the USS-820D must turn off its internal clocks. this occurs when the ssr.suspend register control bit is reset by firmware as described above and is indicated by the USS-820D suspn output pin being asserted. while in suspend mode, the USS-820D must remain powered, but the USS-820D?s power consumption will be reduced to almost zero and will remain in this state until a wake-up is signaled. self-powered devices will most likely not need to turn off power to other application components during suspend. this is indicated to the USS-820D by the ssr.susppo register bit = 0, which should be written by firmware at device initialization time. in such an environment, during suspend, the USS-820D outputs and inputs continue to be driven by the USS-820D and the application, respectively. in addition, the USS-820D bidirectional pins are 3-stated in the USS-820D and driven to 0 or 1 by the application. bus-powered devices will most likely need to turn off power to other application components during suspend. this is indicated to the USS-820D by the ssr.susppo register bit = 1, which should be written by firmware at device initialization time. such devices can be implemented so that the USS-820D suspn output pin controls power to other application compo- nents. issues which must be considered by bus- powered devices are discussed in the special suspend considerations for bus-powered devices section.
agere systems inc. 45 data sheet, rev. 4 june 2001 usb device controller USS-820D suspend and resume behavior (continued) firmware suspend initiate (continued) while the USS-820D is suspended, its internal regis- ters may still be read, presumably only in self-powered devices. the interface timing for such reads is different from register reads during operational mode, and is specified in the register timing characteristics section. register writes must not be attempted while the USS-820D is suspended, with the possible excep- tion of the scr.sreset bit (see the scr.sreset description for details). certain register reads during the nonsuspended state can cause USS-820D device register states to change. these reads are described in the register reads with side effects section. these register reads must not be attempted while the uss- 820d is suspended. hardware resume detect/initiate wake-up can be initiated by either the host or the appli- cation. a host-signaled wake-up (global resume) is indicated when the host drives a k state on the usb bus. a remote wake-up is initiated by the application by asserting the USS-820D rwupn input pin. the uss- 820d can also be awakened by firmware writing a 1 to scr.sreset if mcsr.feat = 1 (see scr.sreset description for details). in these cases, the USS-820D will initiate a wake-up sequence as described in the next section. hardware resume sequence the USS-820D starts a wake-up sequence by asyn- chronously re-enabling its internal oscillator and pll and deasserting the suspn output pin. once the inter- nally generated clocks are stable (a period of 6 ms to 15 ms), then it enables clocks to the entire chip and sets the ssr.resume register bit, which causes an interrupt if scratch.ie_resume register bit = 1. the USS-820D will require up to 15 ms to resume function- ality after a wake-up sequence is initiated. if the wake- up was a remote wake-up, the USS-820D will then drive wake-up signaling (k) on the usb for 12 ms. the USS-820D requires a minimum of 7 ms from the time a remote wake-up is initiated to the time it can begin transmitting resume signaling upstream. this guarantees adherence to the usb specification for twtrsm of 5 ms. firmware resume sequence the USS-820D indicates that the resume sequence is complete by setting the ssr.resume register bit, and possibly causing an interrupt. when firmware is prepared for the application to return to normal opera- tion, it must reset the ssr.resume register bit to allow detection of any subsequent suspend events. special suspend considerations for bus- powered devices in order to meet the usb current requirements while suspended, care must be exercised to guarantee that all board signals connected to the USS-820D are at their proper state. voltages on USS-820D input pins must be guaranteed to be outside the switching threshold region (i.e., either a valid cmos logic 1 or 0). pins that are connected to external, powered-off components must not be driven high. if an external oscillator is used as the clock source for the USS-820D, it will most likely need to be turned off by the USS-820D suspn output pin in order to meet the usb suspend current requirement. when the oscil- lator is turned back on after a resume (when the suspn pin deasserts) and is stabilizing (a period that must not exceed t osc as specified in table 46), its output clock must not have a frequency greater than 12 mhz. as a result, during this stabilization period, the oscillator output must not provide more than 84,000 clocks. the following list describes the expected (or required, as noted) values on the USS-820D pins for devices which turn power off to external components during suspend. such devices must have ssr.susppo = 1 to cause d[7:0], irqn, and sofn to be 3-stated during suspend. they must also have mcsr.bdfeat = 0 while suspended in order to guarantee that usbr and dsa are 3-stated. these register settings avoid the possibility of driving a logic 1 into a powered-off compo- nent, which could result in excessive power consump- tion and possible component damage. external logic refers to components external to the USS-820D. note: board signals which are connected to powered- off components will most likely be naturally pulled to logic 0 by the powered-off component. a[4:0], iocsn, rdn, wrn: input-only pins. their value will be determined by external logic, and must be a logic 0 or 1 to avoid current draw in the uss- 820d.
46 46 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D suspend and resume behavior (continued) special suspend considerations for bus- powered devices (continued) d[7:0], sofn*: bidirectional pins, forced to input mode while suspended (assuming ssr.susppo = 1). their value will be determined by external logic, and must be a logic 0 or 1 to avoid current draw in the USS-820D. irqn, usbr, dsa: 3-statable outputs, forced to 3-state during suspend (assuming ssr.susppo = 1, mcsr.bdfeat = 0). their value will be determined by external logic, and is a don?t care for the USS-820D. dpls, dmns: bidirectional pins, in input mode dur- ing suspend, driven by usb. since they are statically driven to 1 and 0, respectively, there is no current draw in the USS-820D. rwupn: input-only pin, driven to 1 by (powered) external logic during suspend, unless/until a remote wake-up is signalled. suspn: output-only pin, driven to 0 by USS-820D to indicate suspend. xtal1: input connection to internal oscillator. if a crystal is used as a clock source, there are no spe- cial considerations for this pin. if an external oscilla- tor is used as a clock source, this input must be driven to a stable 1 by external logic. reset: driven to 0 during suspend by external logic. dppu: 3-statable output, drives a logic 1 during sus- pend (assuming mcsr.dpen = 1). this is required in case the pin is used to power the external dpls pull-up resistor, which must remain powered during suspend. depending on the device design, the USS-820D register interface signals (rdn, wrn, iocsn) could have unknown values immediately after a suspend because external components have been powered off. in this case, firmware must configure the USS-820D to enable the locking mechanism by setting the mcsr.susploe register bit. this mechanism protects the internal registers from being corrupted in this situation. its behavior is documented in special action required by uss-820/uss-825 after suspend application note (ap97-058cmpr-04). * sofn is an output-only pin during normal operation. in certain chip test modes, this pin functions as an input.
agere systems inc. 47 data sheet, rev. 4 june 2001 usb device controller USS-820D application notes 1. the reset input must remain asserted for a minimum period of time after power is stable. if internal oscillator clocking mode is used, this time is t osc , the amount of time required to allow the internal oscillator output to become stable. if external oscillator clocking mode is used, this time is t rst . the USS-820D wrn and rwupn pins must not both be active (low) at the time that the reset input is deasserted. 2. after changing the size (rxffsz/txffsz), type (isochronous vs. nonisochronous), enabled status (rxepen/ txepen) of a fifo/endpoint or chip features (feat, bdfeat), firmware must guarantee that at least 16 t clk periods have elapsed before attempting to access the fifo data. this is required to allow the internal fifo ram to be reallocated. 3. register writes are triggered by the rising edge of either wrn or iocsn, whichever comes first, and are syn- chronized to the internal 12 mhz clock. therefore, the actual write may not occur until as much as t clk ns after that first rising edge. this latency must be taken into account when performing subsequent register reads or writes. 4. the irqn and sofn pins require external pull-ups or pull-downs if the external controller will be powered off during suspend. in that situation, those pins will be 3-stated until the USS-820D has fully resumed. the pull-up or pull-down is needed to establish the desired level at the controller for the time interval from when the control- ler is powered on to the time when the USS-820D has completed the resume. the same requirements hold for the usbr and dsa outputs if they are connected to devices that will be powered off during suspend. 5. in applications where the external controller is powered off during suspend (firmware has set ssr.susppo), the sofn pin must be connected to an external pull-down even if the pin is not functionally required. the pin is actually bidirectional, where the input mode is only used in chip test modes. the pull-down is required to avoid excessive power consumption by the input stage when the device is suspended. 1394 application support contact information e-mail: 1394support@agere.com absolute maximum ratings stresses in excess of the absolute maximum ratings can cause permanent damage to the device. these are abso- lute stress ratings only. functional operation of the device is not implied at these or any other conditions in excess of those given in the operations sections of this data sheet. exposure to absolute maximum ratings for extended periods can adversely affect device reliability. table 41. absolute maximum ratings table 42. absolute maximum voltage ratings (0 c t a 85 c) table 43. absolute maximum voltage ratings (?20 c t a 0 c) parameter symbol min max unit ambient operating temperature range t a ?20 85 c storage temperature t stg ? 40 125 c power supply voltage with respect to ground v dd ?4.2 v parameter symbol min max unit voltage on any non-usb pin with respect to ground ? v ss ? 0.3 5.5 v parameter symbol min max unit persistent* voltage on any non-usb pin with respect to ground * a persistent voltage level is considered to be one which lasts for more than 25 ns. ?v ss ? 0.3 3.6 v non-persistent* voltage on any non-usb pin with respect to ground ?v ss ? 0.3 5.5 v
48 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D electrical characteristics dc characteristics table 44. dc characteristics (t a = 0 c to 85 c, v dd = 3.3 v 0.165 v, v ss = 0 v) note: these parameters may vary slightly when operating at ambient temperatures below 0 c. parameter symbol test conditions min typ max unit usb signals high-z state data line leakage i lo 0 v < v in < 3.3 v ? 10 ? 10 a differential receiver: common-mode range sensitivity cmr v di ? cmr = 0.8 v to 2.5 v 0 0.2 ? ? v dd ? v v single-ended receiver: low high hysteresis v il v ih v h ? ? ? ? 2.0 0.3 ? ? ? 0.8 ? ? v v v output voltage: low high v ol v oh r l of 1.5 k ? to 3.6 v r l of 15 k ? to gnd ? 2.8 ? ? 0.3 3.465 v v transceiver capacitance cin pin to gnd ? ? 20 pf other signals hysteresis (reset and rwupn only) v h ?0.3??v input voltage: low high v il v ih ? ? ? 2.0 ? ? 0.8 ? v v output voltage (suspn, irqn, usbr, dsa): low high high v ol v oh v oh i ol = 6 ma i ol = ? 6 ma i ol = ? 1 ma ? 2.4 v dd ? 0.15 ? ? ? 0.4 v dd v dd v v v output voltage (d[7:0], sofn, dppu): low high high v ol v oh v oh i ol = 10 ma i ol = ? 10 ma i ol = ? 1 ma ? 2.4 v dd ? 0.1 ? ? ? 0.4 v dd v dd v v v device total supply current: configured preconfigured suspended i d i dp i ds ? ? ? ? ? ? 20 17 2 30 20 10 ma ma a power supply voltage v dd, v dda, v ddt ? ? 3.135 3.3 3.465 v leakage current (d[7:0], sofn) ? ? v in 1.4 v 2.7 v v in 5.5 v ? 10 ? 10 ? ? 10 10 a a leakage current (usbr, dsa, dppu) ?0 v v in 5.5 v ? 10 ? 10 a leakage current (xtal1, a[4:0], rwupn, irqn, reset, iocsn, rdn, wrn) ? ? v in 1.4 v 2.7 v v in 5.5 v ? 1 ? 1 ? ? 1 1 a a
agere systems inc. 49 data sheet, rev. 4 june 2001 usb device controller USS-820D electrical characteristics (continued) power considerations the usb specification places current limits on bus-powered devices. the limit is tighter for a device that has not yet been configured. the tightest limit is for a suspended device. the current values listed in table 44 for a preconfigured device assume fairly low activity (about 5%) on usb. the maximum value for a configured device assumes the device is transmitting 80% of the time on usb. all current values assume a 35 pf load on the package pins. the limit for suspended devices can only be met if careful measures are taken to control the interface to the uss- 820d, as documented in the suspend and resume behavior section. usb transceiver driver characteristics table 45. usb transceiver driver characteristics * at steady-state drive, when used with an external series resistor of 24 ? . parameter symbol test conditions min max unit rise and fall times: (10%?90%) (90%?10%) t r t f oen = 0, c l = 50 pf oen = 0, c l = 50 pf 4 4 20 20 ns ns rise/fall time matching t rfm oen = 0, c l = 50 pf 90 110 % crossover point v crs oen = 0, c l = 50 pf 1.3 2.0 v output impedance* z drv oen = 0 28 43 ?
50 50 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D electrical characteristics (continued) connection requirements usb transceiver connection the physical connection of the USS-820D to the usb bus requires only minimal components to provide proper usb electrical terminations. both dpls and dmns require 24 ? 1% series resis- tors for usb impedance matching. additionally, a 1.5 k ? pull-up resistor is required on dpls for full- speed/low-speed differentiation. 5-8119 figure 9. usb transceiver connection example for bus-powered application when using the USS-820D in a self-powered device, there are some additional considerations. the device must refrain from supplying power through the pull-up resistor if plugged into an unpowered bus. it must also ensure that the dpls and dmns lines are in an appro- priate state when the device is powered but not plugged in. figure 10 shows an example connection to meet these requirements. 5-8120 figure 10. usb transceiver connection example for self-powered application +3.3 v 0.3 v dpls dmns 1.5 k ? 5% 24 ? 1% 24 ? 1% dpls dmns 24 ? 1% 24 ? 1% +3.3 v 0.3 v 1.5 k ? 5% 1.5 m ? close switch only when v bus is powered 1.5 m ?
agere systems inc. 51 data sheet, rev. 4 june 2001 usb device controller USS-820D electrical characteristics (continued) connection requirements (continued) oscillator connection requirements the USS-820D requires an internal 48 mhz clock that it creates from an internal 12 mhz clock via a 4x pll. two methods of clock generation may be used to create this internal 12 mhz clock. figure 11 shows the internal oscil- lator mode which requires only an external 12 mhz crystal and bias capacitors. the values of the capacitors should be chosen as indicated by the crystal manufacturer in order to cause the crystal to operate in a parallel resonant condition. a typical value is 15 pf, but the required value may differ, depending on the specific crystal and board characteristics of the application. alternatively, figure 12 shows the configuration required to input a 12 mhz clock from an external oscillator. in either configuration, the external clock source must have the characteristics defined in table 46. 5-5405.a figure 11. internal oscillator mode 5-5406.a figure 12. external oscillator source table 46. clock characteristics * duty cycle applies to any frequency in an specified range. parameter symbol min typ max unit external clock source frequency f 11.976 12.000 12.024 mhz clock period t cyc 83.1 83.3 83.5 ns clock duty cycle* t cl , t ch 40 50 60 % oscillator stable time t osc ?? 7ms xtal2 xtal1 xtal2 xtal1 12 mhz oscillator
52 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D outline diagrams 44-pin mqfp (USS-820D) dimensions are in millimeters. 5-2111 44 1 10.00 0.20 13.20 0.20 10.00 0.20 13.20 0.20 pin #1 identifier zone 11 12 22 23 33 34 0.80 typ detail a 2.35 max 0.10 seating plane 1.95/2.10 detail b 0.25 max 0.30/0.45 0.20 m 0.130/0.230 detail b 0.25 0.73/1.03 1.60 ref gage plane seating plane detail a
agere systems inc. 53 data sheet, rev. 4 june 2001 usb device controller USS-820D outline diagrams (continued) 48-pin tqfp (uss-820td) dimensions are in millimeters. ordering information * due to size constraints for the 48-pin tqfp package, the device package will be marked uss82tc-db instead of uss820td-db. device code package comcode uss820d-db 44-pin mqfp 108557463 uss820td-db* 48-pin tqfp 108557539 5-2363 pin #1 identifier zone 24 7.00 0.20 1 48 37 12 13 36 25 9.00 0.20 7.00 0.20 1.60 max seating plane detail a 0.08 1.40 0.05 0.50 typ 0.05/0.15 detail b detail b 0.19/0.27 0.08 m 0.106/0.200 detail a 0.45/0.75 gage plane seating plane 1.00 ref 0.25 9.00 0.20
54 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D appendix a. special function register bit names table 47. alphabetical listing of special function register bit names bit name register table page bit name register table page a[6:0] faddr 21 26 rxfif[1:0] rxflg 29 33 advrm txcon 24 27 rxflush rxflg 29 33 advwm rxcon 28 32 rxfull rxflg 29 33 arm rxcon 28 32 rxie epcon 18 21 asof sofh 15 19 rxiso rxcon 28 32 atm txcon 24 27 rxovf rxflg 29 34 bc[7:0] rxcntl 27 31 rxseq rxstat 20 24 bc[7:0] txcntl 23 26 rxsetup rxstat 20 24 bc[9:8] rxcnth 27 31 rxsovw rxstat 20 24 bc[9:8] txcnth 23 26 rxspm epcon 18 21 bdfeat mcsr 36 39 rxstl epcon 18 21 ctlep epcon 18 21 rxurf rxflg 29 34 dpen mcsr 36 39 rxvoid rxstat 20 25 edovw rxstat 20 24 scratch scratch 35 38 epinx[2:0] epindex 17 20 sofack sofh 15 19 feat mcsr 36 39 sofie sofh 15 19 ffsz[1:0] rxcon 28 31 sofodis sofh 15 19 ffsz[1:0] txcon 24 27 sreset scr 30 36 frxd[3:0] sbi 13 17 stovw rxstat 20 24 frxd[7:4] sbi1 14 17 suspdis ssr 31 37 frxie[3:0] sbie 11 16 suspend ssr 31 37 frxie[7:4] sbie1 12 16 susploe mcsr 36 39 ftlock sofh 15 19 susppo ssr 31 37 ftxd[3:0] sbi 13 17 susps mcsr 36 39 ftxd[7:4] sbi1 14 18 t_irq scr 30 36 ftxie[3:0] sbie 11 16 ts[10:8] sofh 15 19 ftxie[7:4] sbie1 12 16 ts[7:0] sofl 16 20 ie_reset scr 30 36 txack txstat 19 22 ie_resume scratch 35 38 txav[3:0] dsav 37 40 ie_susp scr 30 36 txav[7:4] dsav1 38 40 init mcsr 36 39 txclr txcon 24 27 irqlvl scr 30 36 txdat[7:0] txdat 22 26 irqpol scr 30 36 txdsam txstat 19 22 pend pend 34 38 txemp txflg 25 28 pkgid mcsr 36 39 txepen epcon 18 21 reset ssr 31 37 txerr txstat 19 22 resume ssr 31 37 txfif[1:0] txflg 25 28 revrp txcon 24 27 txflush txstat 19 22 revwp rxcon 28 32 txfull txflg 25 30 rwupe scr 30 36 txiso txcon 24 27 rwupr mcsr 36 39 txnake txstat 19 22 rxack rxstat 20 25 txoe epcon 18 21 rxav[3:0] dsav 37 40 txovf txflg 25 28 rxav[7:4] dsav1 38 40 txseq txstat 19 22 rxclr rxcon 28 31 txsovw txstat 19 22 rxdat[7:0] rxdat 26 30 txstl epcon 18 21 rxemp rxflg 29 34 txurf txflg 25 28 rxepen epcon 18 21 txvoid txstat 19 22 rxerr rxstat 20 25 unlocked lock 33 38 rxffrc rxcon 28 31
agere systems inc. 55 data sheet, rev. 4 june 2001 usb device controller USS-820D appendix b. USS-820D register map * indexed by epindex. table 48. USS-820D register map register USS-820D register map addr txdat txdat[7:0] 00* txcntl bc[7:0] 01* txcnth ? bc[9:8] 02* txcon txclr txffsz[1:0] ? txiso atm advrm revrp 03* txflg txfif[1:0] ? txemp txfull txurf txovf 04* rxdat rxdat[7:0] 05* rxcntl bc[7:0] 06* rxcnth ? bc[9:8] 07* rxcon rxclr rxffsz [1:0] rxffrc rxiso arm advwm revwp 08* rxflg rxfif[1:0] ? rxflush rxemp rxfull rxurf rxovf 09* epindex ? epinx[2:0] 0a epcon rxstl txstl ctlep rxspm rxie rxepen txoe txepen 0b* txstat txseq txdsam txnake txflush txsovw txvoid txerr txack 0c* rxstat rxseq rxsetup stovw edovw rxsovw rxvoid rxerr rxack 0d* sofl ts[7:0] 0e sofh sofack asof sofie ftlock sofodis ts[10:8] 0f faddr ? a[6:0] 10 scr irqpol rwupe ie_susp ie_reset sreset irqlvl t_irq ? 11 ssr ? susppo suspdis resume suspend reset 12 sbi frx03 ftx03 frx02 ftx02 frx01 ftx01 frx00 ftx00 14 sbi1 frx07 ftx07 frx06 ftx06 frx05 ftx05 frx04 ftx04 15 sbie frxie3 ftxie3 frxie2 ftxie2 frxie1 ftxie1 frxie0 ftxie0 16 sbie1 frxie7 ftxie7 frxie6 ftxie6 frxie5 ftxie5 frxie4 ftxie4 17 rev rev[7:0] 18 lock ? unlocked 19 pend ? pend 1a scratch ie_resume scratch[6:0] 1b mcsr rwupr init susps pkgid feat bdfeat susploe dpen 1c dsav rxav3 txav3 rxav2 txav2 rxav1 txav1 rxav0 txav0 1d dsav1 rxav7 txav7 rxav6 txav6 rxav5 txav5 rxav4 txav4 1e
56 56 agere systems inc. data sheet, rev. 4 june 2001 usb device controller USS-820D appendix c. changes from uss-820/ uss-825 revision b to c note: for revision c, the uss-825b has been renamed uss-820tc. 1. hardware revision register (rev) changed from 1.0 to 1.1. 2. from the usb system and firmware points of view, the uss-820c will appear functionally equivalent to the uss-820b if a 1 is never written by firmware to mcsr[3:2] or txstat[6:5] (all previously marked as reserved). the single exception is the rev register as described above. 3. new register bits (feat, bdfeat) are added to enable new features. bdfeat enables those fea- tures which could impact existing boards. this could only be an issue if nc pins were used as connection points for other board signals. feat enables all other features as indicated. feat is mcsr[3]; bdfeat is mcsr[2]. 4. new fifo status bits (rxav/txav), one per fifo, added to indicate receive data set(s) available (rxfif > 00) or empty transmit data set(s) avail- able (txfif < 11). if txdsam = 1, transmit fifo status bits are set if the device sends a nak in response to an in packet when txfif = 00. the 16 register bits are formatted into two new regis- ters (dsav = address 1d, dsav1 = address 1e) in the same format as sbi/sbi1. these new read- only bits can allow firmware to operate more effi- ciently, because their use requires less polling overhead. register bits always read 0 unless feat = 1 or txdsam = 1. 5. a logical or of new fifo status bits (rxav/txav) is brought out to a package pin (dsa). package pin is always 3-stated if bdfeat = 0. uses pin 15 in 44-pin package, pin 16 in 48-pin package. 6. new nonisochronous transmit mode. if enabled (by new register bit txnake = txstat[5]), when the uss-820c responds to an in token with a nak because of no data sets being present (txfif = 00), an interrupt is generated, setting the appropri- ate sbi/sbi1 bit. new register bit txdsam (txstat[6]) allows this condition to set the new dsav register bit and assert the new dsa output pin (assuming they are enabled). this mode changes the meaning of txvoid to indicate that such a nak was sent, and it is the responsibility of firmware to clear txvoid. while txvoid = 1, the corresponding sbi/sbi1 register bit will remain set as well. 7. transmit isochronous behavior changed to discard old data packets at the end of the intended frame if not read out by a host in (only enabled if feat = 1). data sets are not visible to the host until the first sof following the data set write. at the start of a series of transfers, txfif will equal 00, which could allow firmware to write two data sets during that same frame. in that case, the older set is flushed by hardware at the first sof. 8. receive isochronous behavior changed to flush old data packets at the end of the intended frame if not read out by firmware (only enabled if feat = 1). this flush decrements rxfif and sets the rxflush register bit (rxflg[4]), which firmware must check before setting rxffrc. while rxflush is set, the effect of firmware rxdat reads (fifo pointer/flag changes) is blocked, to avoid possible corruption of a new data set. if firm- ware detects that rxflush = 1, it must discard the data set just read, since it is possibly truncated. firmware must still set rxffrc in this situation, which resets rxflush to 0. 9. asof behavior changed to not automatically reset when sofodis = 0 if feat = 1. 10. for nonisochronous endpoints, ffsz = 2 indicates 8 bytes, ffsz = 3 indicates 32 bytes (both are interpreted as 64 bytes in the uss-820 revision b). this will potentially allow more efficient usage of the shared fifo space. only enabled if feat = 1. 11. usb-reset-detected condition clears the faddr register (if feat = 1). this avoids the potential case where firmware is too slow in resetting faddr after usb reset such that the host real- locates the address to some other device and sends traffic to that device, which is misinterpreted by the uss-820c as intended for it. no other regis- ter bits are cleared by usb reset. 12. usb-reset-detected condition brought out to pack- age pin (usbr), allowing the external controller to clear out a locked up device. output is always 3- stated if bdfeat = 0. uses pin 18 of 44-pin pack- age, pin 19 of 48-pin package. 13. firmware provided means to resume and reset device if suspended. when suspended, if suspp0 = 0, susploe = 0, feat = 1, a firmware write of 1 to scr bit 3 (sreset) causes a remote wake-up type of event (without resume signaling). after the wake-up, when clocks are turned on, the sreset bit will be set and will take effect (i.e., the uss-820c will be reset).
agere systems inc. 57 data sheet, rev. 4 june 2001 usb device controller USS-820D appendix c. changes from uss-820/ uss-825 revision b to c (continued) 14. remote-wake-up-remember condition is visible as a register bit (rwupr). register bit always reads a 0 unless feat = 1. rwupr is mcsr[7]. 15. additional/updated electrical characteristics related to the new 0.25 m process (power, hysteresis leakage current) are included. 16. the v dd5v pin is no longer required?may be treated as no connect. appendix d. changes from uss-820/ uss-820t revision c to d 1. all (4) uss-820c/uss-820tc advisory items are corrected. 2. value of rev register is changed from 11h to 13h.
agere systems inc. reserves the right to make changes to the product(s) or information contained herein without notice. no liab ility is assumed as a result of their use or application. copyright ? 2001 agere systems inc. all rights reserved printed in u.s.a. june 2001 ds00-146cmpr-4 (replaces ds00-146cmpr-3) for additional information, contact your agere systems account manager or the following: internet: http://www.agere.com e-mail: docmaster@micro.lucent.com n. america: agere systems inc., 555 union boulevard, room 30l-15p-ba, allentown, pa 18109-3286 1-800-372-2447 , fax 610-712-4106 (in canada: 1-800-553-2448 , fax 610-712-4106) asia pacific: agere systems singapore pte. ltd., 77 science park drive, #03-18 cintech iii, singapore 118256 tel. (65) 778 8833 , fax (65) 777 7495 china: agere systems (shanghai) co., ltd., 33/f jin mao tower, 88 century boulevard pudong, shanghai 200121 prc tel. (86) 21 50471212 , fax (86) 21 50472266 japan: agere systems japan ltd., 7-18, higashi-gotanda 2-chome, shinagawa-ku, tokyo 141, japan tel. (81) 3 5421 1600 , fax (81) 3 5421 1700 europe: data requests: dataline: tel. (44) 7000 582 368 , fax (44) 1189 328 148 technical inquiries: germany: (49) 89 95086 0 (munich), united kingdom: (44) 1344 865 900 (ascot), france: (33) 1 40 83 68 00 (paris), sweden: (46) 8 594 607 00 (stockholm), finland: (358) 9 3507670 (helsinki), italy: (39) 02 6608131 (milan), spain: (34) 1 807 1441 (madrid)

▲Up To Search▲

Price & Availability of USS-820D

	To Download USS-820D Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .